public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Judith Mendez <jm@ti•com>
To: Judith Mendez <jm@ti•com>, Nishanth Menon <nm@ti•com>,
	Vignesh Raghavendra <vigneshr@ti•com>
Cc: Tero Kristo <kristo@kernel•org>, Rob Herring <robh@kernel•org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel•org>,
	Conor Dooley <conor+dt@kernel•org>,
	<linux-arm-kernel@lists•infradead.org>,
	<devicetree@vger•kernel.org>, <linux-kernel@vger•kernel.org>,
	Andrew Davis <afd@ti•com>, Bryan Brattlof <bb@ti•com>,
	Jason Kridner <jkridner@gmail•com>,
	Robert Nelson <robertcnelson@gmail•com>,
	Conor Dooley <conor.dooley@microchip•com>
Subject: [PATCH v6 0/3] arm64: dts/bindings: Add support for BeagleBadge
Date: Wed, 3 Jun 2026 14:23:02 -0500	[thread overview]
Message-ID: <20260603192305.1347908-1-jm@ti.com> (raw)

Hi,

BeagleBoard.org BeagleBadge[1] is a compact, affordable open source
hardware [2] single board computer based on the Texas Instruments AM62L3
SoC designed for IoT and embedded applications. Add base support for
the same.

SD boot:
Link: https://gist.github.com/jmenti/e9e95848336fda0e4b5acb37f2fe64a0

This patch series adds:
- Device tree bindings update for am62l3-badge
- Device tree source for BeagleBadge board
- Defconfig: drivers for BeagleBadge

Changelog since v5:
DTS
- Fixed aliases/chosen nodes
- Sort Makefile items alphabetically
- Use dual license: GPL-2.0-only or MIT

v5
Link: https://lore.kernel.org/all/20260526235417.1326187-1-jm@ti.com/
v4
Link: https://lore.kernel.org/all/20260515153541.294698-1-jm@ti.com/
v3
Link: https://lore.kernel.org/all/20260513233447.2713737-1-jm@ti.com/
V2
Link: https://lore.kernel.org/all/20260508230341.1891450-1-jm@ti.com/
V1
Link: https://lore.kernel.org/all/20260501233148.4180391-1-jm@ti.com/

Patch series depends on:
Link: https://lore.kernel.org/all/20260513231154.2703292-1-jm@ti.com/

[1] https://www.beagleboard.org/boards/beaglebadge
[2] https://github.com/beagleboard/BeagleBadge/blob/main/design/BeagleBadge_RevA_V0.7_SCH_251107.pdf

Judith Mendez (3):
  dt-bindings: arm: ti: Add am62l3-beaglebadge
  arm64: dts: ti: Add k3-am62l3-beaglebadge
  arm64: defconfig: Enable drivers for BeagleBadge

 .../devicetree/bindings/arm/ti/k3.yaml        |   1 +
 arch/arm64/boot/dts/ti/Makefile               |   1 +
 .../boot/dts/ti/k3-am62l3-beaglebadge.dts     | 657 ++++++++++++++++++
 arch/arm64/configs/defconfig                  |   5 +
 4 files changed, 664 insertions(+)
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts

-- 
2.54.0



             reply	other threads:[~2026-06-03 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 19:23 Judith Mendez [this message]
2026-06-03 19:23 ` [PATCH v6 1/3] dt-bindings: arm: ti: Add am62l3-beaglebadge Judith Mendez
2026-06-03 19:23 ` [PATCH v6 2/3] arm64: dts: ti: Add k3-am62l3-beaglebadge Judith Mendez
2026-06-03 19:23 ` [PATCH v6 3/3] arm64: defconfig: Enable drivers for BeagleBadge Judith Mendez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260603192305.1347908-1-jm@ti.com \
    --to=jm@ti$(echo .)com \
    --cc=afd@ti$(echo .)com \
    --cc=bb@ti$(echo .)com \
    --cc=conor+dt@kernel$(echo .)org \
    --cc=conor.dooley@microchip$(echo .)com \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=jkridner@gmail$(echo .)com \
    --cc=kristo@kernel$(echo .)org \
    --cc=krzk+dt@kernel$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=nm@ti$(echo .)com \
    --cc=robertcnelson@gmail$(echo .)com \
    --cc=robh@kernel$(echo .)org \
    --cc=vigneshr@ti$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox