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 v5 0/3] arm64: dts/bindings: Add support for BeagleBadge
Date: Tue, 26 May 2026 18:54:14 -0500 [thread overview]
Message-ID: <20260526235417.1326187-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/8818fa277597de927dd2b42ab1d2552f
This patch series adds:
- Device tree bindings update for am62l3-badge
- Device tree source for BeagleBadge board
- Defconfig: drivers for BeagleBadge
Changelog since v4:
- Canonical URL fixed
- Switch gpio -> gpios in voltage regulator nodes
- Regulator-always-on removed in sensor_3v3
- Add bootph-all on pinmux nodes
- Fix gpio-line-names formatting
- Nodes: sdhci2, wlan_en regulator, & pinmux removed
- USB aliases removed
- Pickup Conor's review tag
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 | 658 ++++++++++++++++++
arch/arm64/configs/defconfig | 5 +
4 files changed, 665 insertions(+)
create mode 100644 arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts
--
2.54.0
next reply other threads:[~2026-05-26 23:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 23:54 Judith Mendez [this message]
2026-05-26 23:54 ` [PATCH v5 1/3] dt-bindings: arm: ti: Add am62l3-beaglebadge Judith Mendez
2026-05-26 23:54 ` [PATCH v5 2/3] arm64: dts: ti: Add k3-am62l3-beaglebadge Judith Mendez
2026-05-28 10:52 ` Vignesh Raghavendra
2026-05-28 22:04 ` Judith Mendez
2026-05-26 23:54 ` [PATCH v5 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=20260526235417.1326187-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