Skip to contentSkip to conversation

arm64: dts/bindings: Add support for BeagleBadge

PATCH Superseded Judith Mendez 4 participants 11 messages May 15 – May 26

Subsystems (2)

v4 of 6 Superseded Latest is v6 →

lore
Share & tools
lore
#0 lore raw

v4 cover arm64: dts/bindings: Add support for BeagleBadge

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:

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

Changelog since v3:
- Fix newline in commit messages
- Drop vendor URLs
DTS:
- Add bootph flags in wakup i2c & PMIC nodes for completeness
- Drop unneeded header files

v3

V2

V1

Patch series depends on:

[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     | 700 ++++++++++++++++++
 arch/arm64/configs/defconfig                  |   5 +
 4 files changed, 707 insertions(+)
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts
Signature · 1 line
2.54.0
#1 lore raw

PATCH v4 1/3 dt-bindings: arm: ti: Add am62l3-beaglebadge

This board is based on ti,am62l3.

https://github.com/beagleboard/BeagleBadge

---
Changelog since v3:
- Add missing newline in commit message
- Drop beagleboard url

---
 Documentation/devicetree/bindings/arm/ti/k3.yaml | 1 +
 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/arm/ti/k3.yaml +1 -0
index 2a6a9441c23de..d9cd3fb712fdd 100644
@@ -40,6 +40,7 @@ properties:
       - description: K3 AM62L3 SoC and Boards
         items:
           - enum:
+              - beagle,am62l3-beaglebadge
               - ti,am62l3-evm
           - const: ti,am62l3
 
Signature · 1 line
2.54.0
#3 lore raw

PATCH v4 2/3 arm64: dts: ti: Add k3-am62l3-beaglebadge

In reply to Judith Mendez

BeagleBoard.org BeagleBadge is a compact, affordable open source hardware single board computer based on the Texas Instruments AM62L3 SoC designed for IoT and embedded applications with low power consumption. Expansion is provided over open standards based headers including QWIIC and GPIO interfaces.

https://github.com/beagleboard/BeagleBadge

---
Changelog since v3:
- Add missing newline in commit message
- Drop beagleboard URL
- Drop uneeded header files
- Add boothph flags in wkup_i2c0 & PMC nodes

---
 arch/arm64/boot/dts/ti/Makefile               |   1 +
 .../boot/dts/ti/k3-am62l3-beaglebadge.dts     | 700 ++++++++++++++++++
 2 files changed, 701 insertions(+)
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts
arch/arm64/boot/dts/ti/Makefile +1 -0
index 5269c9619b65c..4e377ca011cd8 100644
@@ -41,6 +41,7 @@ dtb-$(CONFIG_ARCH_K3) += k3-am62d2-evm.dtb
 
 # Boards with AM62Lx SoCs
 dtb-$(CONFIG_ARCH_K3) += k3-am62l3-evm.dtb
+dtb-$(CONFIG_ARCH_K3) += k3-am62l3-beaglebadge.dtb
 
 # Boards with AM62Px SoC
 dtb-$(CONFIG_ARCH_K3) += k3-am62p5-sk.dtb
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +700 -0

700 lines not on this page · raw message

Signature · 1 line
2.54.0
#4 lore raw

Re: [PATCH v4 2/3] arm64: dts: ti: Add k3-am62l3-beaglebadge

Thank you for your contribution! Sashiko AI review found 5 potential issue(s) to consider: - [High] Unmanaged Board Control GPIOs (Missing GPIO Hogs / Regulators) for `BOOST_5V_ENA` and…

Thank you for your contribution! Sashiko AI review found 5 potential issue(s) to consider:
- [High] Unmanaged Board Control GPIOs (Missing GPIO Hogs / Regulators) for BOOST_5V_ENA and USB_HUB_RST.
- [High] Driver/DTB Interface Violation: microchip,spi-present-mask length mismatch.
- [High] Missing bootph-all property on referenced pinctrl nodes will cause U-Boot SPL probe failures.
- [Medium] Misplaced Consumer Pinctrl Configurations on the &gpio0 provider node.
- [Low] Deprecated gpio property used instead of gpios in regulator-fixed nodes.
--

commit 535e2cddc8d18ba0025f3f27f6e67f150156d239
Author: Judith Mendez <[email protected]>
arm64: dts: ti: Add k3-am62l3-beaglebadge

This patch introduces the device tree for the BeagleBoard.org BeagleBadge, a compact single board computer based on the TI AM62L3 SoC. It provides the initial hardware description including regulators, GPIOs, pinmux configurations, and basic peripherals.

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +0 -0
new file mode 100644
index 0000000000000..30fc9c83b1f44

[ ... ]

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 200

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+	vdd_3v3_sd: regulator-3 {
+		/* TPS22918DBVR */
+		compatible = "regulator-fixed";
+		regulator-name = "VDD_3V3_SD";
+		regulator-min-microvolt = <3300000>;
+		regulator-max-microvolt = <3300000>;
+		vin-supply = <&vdd_3v3>;
+		regulator-boot-on;
+		enable-active-high;
+		gpio = <&gpio0 16 GPIO_ACTIVE_HIGH>;

This isn't a bug, but could the gpios property be used here instead of the deprecated gpio property? The wlan_en node later in this file correctly uses the plural form.

Quoted 6 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +6 -0
+		pinctrl-names = "default";
+		pinctrl-0 = <&vdd_3v3_sd_ena_pins_default>;
+		bootph-all;
+	};
+
+	sensor_3v3: regulator-4 {

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 216

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+		/* TPS22918DBVR */
+		compatible = "regulator-fixed";
+		regulator-name = "Sensor_3V3";
+		regulator-min-microvolt = <3300000>;
+		regulator-max-microvolt = <3300000>;
+		vin-supply = <&vdd_3v3>;
+		regulator-boot-on;
+		regulator-always-on;
+		enable-active-high;
+		gpio = <&wkup_gpio0 1 GPIO_ACTIVE_HIGH>;

Could this also be updated to use the gpios property?

[ ... ]

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 270

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+	usr_button_pins_default: usr-button-default-pins {
+		pinctrl-single,pins = <
+			AM62LX_IOPAD(0x00a4, PIN_INPUT, 7) /* (H18) GPMC0_AD11.GPIO0_26 */
+			AM62LX_IOPAD(0x01e4, PIN_INPUT, 7) /* (D16) EXT_REFCLK1.GPIO0_104 */
+			AM62LX_IOPAD(0x00c0, PIN_INPUT, 7) /* (N19) GPMC0_ADVn_ALE.GPIO0_32 */
+			AM62LX_IOPAD(0x00e8, PIN_INPUT, 7) /* (L19) GPMC0_CSn1.GPIO0_42 */
+			AM62LX_IOPAD(0x00b8, PIN_INPUT, 7) /* (L21) GPMC0_CLK.GPIO0_31 */
+			AM62LX_IOPAD(0x01c0, PIN_INPUT, 7) /* (B13) UART0_RTSn.GPIO0_95 */
+		>;
+	};

Because the gpio0 node later in the file includes the bootph-all property and references this node, does this node also need bootph-all? Without it, U-Boot's fdtgrep might strip this node, leaving a dangling phandle and causing probe failures in SPL.

[ ... ]

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 307

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +5 -0
+	sensor_3v3_ena_pins_default: sensor-3v3-ena-default-pins {
+		pinctrl-single,pins = <
+			AM62LX_IOPAD(0x004, PIN_OUTPUT, 7) /* (AA23) WKUP_UART0_TXD.WKUP_GPIO0_1 */
+		>;
+	};

Does this node also need the bootph-all property? The sensor_3v3 regulator node uses this pinctrl configuration and has bootph-all.

[ ... ]

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 425

Quoted 8 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +8 -0
+	lora_control_pins_default: lora-control-default-pins {
+		pinctrl-single,pins = <
+			AM62LX_IOPAD(0x00c8, PIN_OUTPUT, 7) /* (M19) GPMC0_WEn.GPIO0_34 */
+			AM62LX_IOPAD(0x00e4, PIN_OUTPUT, 7) /* (L20) GPMC0_CSn0.GPIO0_41 */
+			AM62LX_IOPAD(0x01a4, PIN_INPUT, 7) /* (D11) SPI0_CS1.GPIO0_88 */
+			AM62LX_IOPAD(0x01bc, PIN_INPUT, 7) /* (B14) UART0_CTSn.GPIO0_94 */
+		>;
+	};

Same question here regarding the bootph-all property since this is referenced by the gpio0 node.

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 435

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+
+	gpio0_pins_default: gpio0-default-pins {
+		pinctrl-single,pins = <
+			AM62LX_IOPAD(0x0078, PIN_OUTPUT, 7) /* (L22) GPMC0_AD0.GPIO0_15 */
+			AM62LX_IOPAD(0x00e0, PIN_INPUT, 7) /* (M21) GPMC0_DIR.GPIO0_40 */
+			AM62LX_IOPAD(0x00ec, PIN_OUTPUT, 7) /* (M23) GPMC0_CSn2.GPIO0_43 */
+			AM62LX_IOPAD(0x00f0, PIN_INPUT, 7) /* (M22) GPMC0_CSn3.GPIO0_44 */
+			AM62LX_IOPAD(0x0194, PIN_OUTPUT, 7) /* (B11) MCASP0_AFSX.GPIO0_84 */
+		>;
+	};

Does this node also need bootph-all to match the gpio0 node?

Also, I noticed that GPIO0_15 (BOOST_5V_ENA) and GPIO0_43 (USB_HUB_RST) are configured as PIN_OUTPUT here. Because configuring PIN_OUTPUT in pinctrl only sets the pad multiplexing and does not actively drive a logic level on the GPIO controller, will these pins remain floating?

Should there be a gpio-hog or consumer regulator node to manage the direction and logic level for these control pins?

[ ... ]

Quoted 6 lines

+&gpio0 {

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +5 -0
+	gpio-line-names ="","","","","","","","","","",									/* 0-9 */
+			 "","","","","","BOOST_5V_ENA","VDD_3V3_SD_ENA","","","",					/* 10-19 */
+			 "","","","","","MCP23S18_RESET","BTN_SELECT","","","",						/* 20-29 */
+			 "","BTN_LEFT","BTN_UP","","LORA_RESET","","","","","",						/* 30-39 */
+			 "FUEL_GAUGE_BATLOW","LORA_RFSW","BTN_DOWN","USB_HUB_RST","MIKROBUS_INT","","","","","",	/* 40-49 */

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 586

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+			 "","WLAN_EN","","","","","","","","",								/* 50-59 */
+			 "","","","","","","","","","",									/* 60-69 */
+			 "","","","","","","","","","",									/* 70-79 */
+			 "","","","","MIKROBUS_RST","","","","LORA_BUSY","",						/* 80-89 */
+			 "","","","","LORA_DIO","BTN_RIGHT","","","","",						/* 90-99 */
+			 "","","","","BTN_BACK","","","","","",								/* 100-109 */
+			 "","","","","","","","","","",									/* 110-119 */
+			 "","","SD_CD","","","";									/* 120-125 */
+	pinctrl-names = "default";
+	pinctrl-0 = <&gpio0_pins_default>, <&usr_button_pins_default>, <&lora_control_pins_default>;

Is it expected to place the pinctrl configurations for consumer devices (usr_button_pins_default and lora_control_pins_default) on the gpio0 provider node?

This causes the pins to be claimed when the GPIO controller probes. Could these be moved to the respective consumer device nodes instead?

[ ... ]

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 692

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+	mcp23s18: gpio@0 {
+		compatible = "microchip,mcp23s18";
+		reg = <0>;
+		spi-max-frequency = <10000000>;
+		gpio-controller;
+		#gpio-cells = <2>;
+		reset-gpios = <&gpio0 25 GPIO_ACTIVE_LOW>;
+		pinctrl-names = "default";
+		pinctrl-0 = <&mcp23s18_reset_pins_default>;
+		microchip,spi-present-mask = /bits/ 8 <0x01>;

Will this cause a probe failure in the pinctrl-mcp23s08_spi driver?

The driver uses device_property_read_u32() to parse the microchip,spi-present-mask property. Because the property is defined here as an 8-bit value, the property read API will see a length mismatch and might return -EOVERFLOW.

Could this be specified as a standard 32-bit cell (i.e., <0x01>)?

Quoted 2 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +2 -0
+	};
+};
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=2
maintainer
#5 lore raw

Re: [PATCH v4 2/3] arm64: dts: ti: Add k3-am62l3-beaglebadge

In reply to Judith Mendez
Quoted 7 lines · Judith Mendez

BeagleBoard.org BeagleBadge is a compact, affordable open source hardware single board computer based on the Texas Instruments AM62L3 SoC designed for IoT and embedded applications with low power consumption. Expansion is provided over open standards based headers including QWIIC and GPIO interfaces.

https://github.com/beagleboard/BeagleBadge

Why not use https://www.beagleboard.org/boards/beaglebadge ?

Quoted 34 lines

---
Changelog since v3:
- Add missing newline in commit message
- Drop beagleboard URL
- Drop uneeded header files
- Add boothph flags in wkup_i2c0 & PMC nodes

---
 arch/arm64/boot/dts/ti/Makefile               |   1 +
 .../boot/dts/ti/k3-am62l3-beaglebadge.dts     | 700 ++++++++++++++++++
 2 files changed, 701 insertions(+)
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts
arch/arm64/boot/dts/ti/Makefile +1 -0
index 5269c9619b65c..4e377ca011cd8 100644
@@ -41,6 +41,7 @@ dtb-$(CONFIG_ARCH_K3) += k3-am62d2-evm.dtb
 
 # Boards with AM62Lx SoCs
 dtb-$(CONFIG_ARCH_K3) += k3-am62l3-evm.dtb
+dtb-$(CONFIG_ARCH_K3) += k3-am62l3-beaglebadge.dtb
 
 # Boards with AM62Px SoC
 dtb-$(CONFIG_ARCH_K3) += k3-am62p5-sk.dtb
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +0 -0
new file mode 100644
index 0000000000000..30fc9c83b1f44

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 5

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +5 -0
@@ -0,0 +1,700 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * https://www.beagleboard.org/boards/beaglebadge
+ *
+ * Copyright (C) 2026 Texas Instruments Incorporated - https://www.ti.com/

Seeing the tags, I assume no BeagleBoard.org member contributions?

Quoted 20 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +20 -0
+ */
+
+/dts-v1/;
+
+#include <dt-bindings/gpio/gpio.h>
+#include <dt-bindings/input/input.h>
+#include <dt-bindings/leds/common.h>
+#include "k3-am62l3.dtsi"
+#include "k3-pinctrl.h"
+
+/ {
+	compatible = "beagle,am62l3-beaglebadge", "ti,am62l3";
+	model = "BeagleBoard.org BeagleBadge";
+
+	chosen {
+		stdout-path = &uart0;
+	};
+
+	aliases {
+		gpio0 = &gpio0;

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 35

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+		gpio2 = &wkup_gpio0;
+		i2c0 = &i2c0;
+		i2c1 = &i2c1;
+		i2c2 = &i2c2;
+		i2c4 = &wkup_i2c0;
+		mmc1 = &sdhci1;
+		mmc2 = &sdhci2;
+		serial3 = &uart1;
+		usb0 = &usb0;
+		usb1 = &usb1;

is this valid?
git grep of_alias_ driver/usb/

am I missing something?

Quoted 14 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +14 -0
+	};
+
+	memory@80000000 {
+		/* 256MB */
+		reg = <0x00000000 0x80000000 0x00000000 0x10000000>;
+		device_type = "memory";
+		bootph-all;
+	};
+
+	thermal-zones {
+		wkup0-thermal {
+			polling-delay-passive = <250>;	/* milliSeconds */
+			polling-delay = <500>;		/* milliSeconds */
+			thermal-sensors = <&vtm0 0>;

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 59

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+
+			trips {
+				crit0 {
+					temperature = <125000>;
+					hysteresis = <2000>;
+					type = "critical";
+				};
+			};
+		};
+	};

This is better done by having something like arch/arm64/boot/dts/ti/k3-am62l-industrial-thermal.dtsi

[..]

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 214

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+
+	sensor_3v3: regulator-4 {
+		/* TPS22918DBVR */
+		compatible = "regulator-fixed";
+		regulator-name = "Sensor_3V3";
+		regulator-min-microvolt = <3300000>;
+		regulator-max-microvolt = <3300000>;
+		vin-supply = <&vdd_3v3>;
+		regulator-boot-on;
+		regulator-always-on;

Why sensor supply is always on?

Quoted 19 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +19 -0
+		enable-active-high;
+		gpio = <&wkup_gpio0 1 GPIO_ACTIVE_HIGH>;
+		pinctrl-names = "default";
+		pinctrl-0 = <&sensor_3v3_ena_pins_default>;
+		bootph-all;
+	};
+
+	wlan_en: regulator-5 {
+		compatible = "regulator-fixed";
+		regulator-name = "wlan_en";
+		regulator-min-microvolt = <1800000>;
+		regulator-max-microvolt = <1800000>;
+		enable-active-high;
+		gpios = <&gpio0 51 GPIO_ACTIVE_HIGH>;
+		pinctrl-names = "default";
+		pinctrl-0 = <&wlan_en_pins_default>;
+	};
+};
+

[..]

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 270

Quoted 11 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +11 -0
+
+	usr_button_pins_default: usr-button-default-pins {
+		pinctrl-single,pins = <
+			AM62LX_IOPAD(0x00a4, PIN_INPUT, 7) /* (H18) GPMC0_AD11.GPIO0_26 */
+			AM62LX_IOPAD(0x01e4, PIN_INPUT, 7) /* (D16) EXT_REFCLK1.GPIO0_104 */
+			AM62LX_IOPAD(0x00c0, PIN_INPUT, 7) /* (N19) GPMC0_ADVn_ALE.GPIO0_32 */
+			AM62LX_IOPAD(0x00e8, PIN_INPUT, 7) /* (L19) GPMC0_CSn1.GPIO0_42 */
+			AM62LX_IOPAD(0x00b8, PIN_INPUT, 7) /* (L21) GPMC0_CLK.GPIO0_31 */
+			AM62LX_IOPAD(0x01c0, PIN_INPUT, 7) /* (B13) UART0_RTSn.GPIO0_95 */
+		>;
+	};

no wakeup from usr buttons?

[...]

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 572

Quoted 4 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +4 -0
+};
+
+&gpio0 {
+	gpio-line-names ="","","","","","","","","","",									/* 0-9 */

space after that =

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 584

Quoted 12 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +12 -0
+			 "","","","","","BOOST_5V_ENA","VDD_3V3_SD_ENA","","","",					/* 10-19 */
+			 "","","","","","MCP23S18_RESET","BTN_SELECT","","","",						/* 20-29 */
+			 "","BTN_LEFT","BTN_UP","","LORA_RESET","","","","","",						/* 30-39 */
+			 "FUEL_GAUGE_BATLOW","LORA_RFSW","BTN_DOWN","USB_HUB_RST","MIKROBUS_INT","","","","","",	/* 40-49 */
+			 "","WLAN_EN","","","","","","","","",								/* 50-59 */
+			 "","","","","","","","","","",									/* 60-69 */
+			 "","","","","","","","","","",									/* 70-79 */
+			 "","","","","MIKROBUS_RST","","","","LORA_BUSY","",						/* 80-89 */
+			 "","","","","LORA_DIO","BTN_RIGHT","","","","",						/* 90-99 */
+			 "","","","","BTN_BACK","","","","","",								/* 100-109 */
+			 "","","","","","","","","","",									/* 110-119 */
+			 "","","SD_CD","","","";									/* 120-125 */

Could you keep these under 100 chars?

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 592

Quoted 8 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +8 -0
+	pinctrl-names = "default";
+	pinctrl-0 = <&gpio0_pins_default>, <&usr_button_pins_default>, <&lora_control_pins_default>;
+	bootph-all;
+	status = "okay";
+};
+
+&wkup_gpio0 {
+	gpio-line-names ="","SENSOR_3V3_ENA","","","","","","";								/* 0-7 */

same

Quoted 19 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +19 -0
+	bootph-all;
+	status = "okay";
+};
+
+&sdhci1 {
+	/* SD/MMC */
+	vmmc-supply = <&vdd_3v3_sd>;
+	disable-wp;
+	cd-gpios = <&gpio0 122 GPIO_ACTIVE_LOW>;
+	cd-debounce-delay-ms = <100>;
+	ti,fails-without-test-cd;
+	pinctrl-names = "default";
+	pinctrl-0 = <&mmc1_pins_default>;
+	bootph-all;
+	status = "okay";
+};
+
+&sdhci2 {
+	vmmc-supply = <&wlan_en>;

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 621

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+	bus-width = <4>;
+	non-removable;
+	cap-power-off-card;
+	keep-power-in-suspend;
+	pinctrl-names = "default";
+	pinctrl-0 = <&mmc2_pins_default>;
+	ti,driver-strength-ohm = <50>;
+	ti,fails-without-test-cd;
+	status = "okay";
+};

Why not introduce the sdhci2 and supplies once we get wlan driver in upstream?

[...]

Signature · 4 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource
#6 lore raw

Re: [PATCH v4 2/3] arm64: dts: ti: Add k3-am62l3-beaglebadge

Quoted 10 lines · Nishanth Menon
Quoted 7 lines · Judith Mendez

BeagleBoard.org BeagleBadge is a compact, affordable open source hardware single board computer based on the Texas Instruments AM62L3 SoC designed for IoT and embedded applications with low power consumption. Expansion is provided over open standards based headers including QWIIC and GPIO interfaces.

https://github.com/beagleboard/BeagleBadge

Why not use https://www.beagleboard.org/boards/beaglebadge ?

Will switch link

Quoted 26 lines
Quoted 26 lines

---
Changelog since v3:
- Add missing newline in commit message
- Drop beagleboard URL
- Drop uneeded header files
- Add boothph flags in wkup_i2c0 & PMC nodes

---
  arch/arm64/boot/dts/ti/Makefile               |   1 +
  .../boot/dts/ti/k3-am62l3-beaglebadge.dts     | 700 ++++++++++++++++++
  2 files changed, 701 insertions(+)

create mode 100644 arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts

arch/arm64/boot/dts/ti/Makefile +1 -0
index 5269c9619b65c..4e377ca011cd8 100644
@@ -41,6 +41,7 @@ dtb-$(CONFIG_ARCH_K3) += k3-am62d2-evm.dtb
 
  # Boards with AM62Lx SoCs
  dtb-$(CONFIG_ARCH_K3) += k3-am62l3-evm.dtb
+dtb-$(CONFIG_ARCH_K3) += k3-am62l3-beaglebadge.dtb
 
Quoted 15 lines

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 5

Quoted 13 lines
arch/arm64/boot/dts/ti/Makefile +0 -0
  # Boards with AM62Px SoC
  dtb-$(CONFIG_ARCH_K3) += k3-am62p5-sk.dtb
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +5 -0
new file mode 100644
index 0000000000000..30fc9c83b1f44
@@ -0,0 +1,700 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * https://www.beagleboard.org/boards/beaglebadge
+ *
+ * Copyright (C) 2026 Texas Instruments Incorporated - https://www.ti.com/

Seeing the tags, I assume no BeagleBoard.org member contributions?

Not yet ^.^

Quoted 56 lines
Quoted 21 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +20 -0
+ */
+
+/dts-v1/;
+
+#include <dt-bindings/gpio/gpio.h>
+#include <dt-bindings/input/input.h>
+#include <dt-bindings/leds/common.h>
+#include "k3-am62l3.dtsi"
+#include "k3-pinctrl.h"
+
+/ {
+	compatible = "beagle,am62l3-beaglebadge", "ti,am62l3";
+	model = "BeagleBoard.org BeagleBadge";
+
+	chosen {
+		stdout-path = &uart0;
+	};
+
+	aliases {
+		gpio0 = &gpio0;

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 35

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+		gpio2 = &wkup_gpio0;
+		i2c0 = &i2c0;
+		i2c1 = &i2c1;
+		i2c2 = &i2c2;
+		i2c4 = &wkup_i2c0;
+		mmc1 = &sdhci1;
+		mmc2 = &sdhci2;
+		serial3 = &uart1;
+		usb0 = &usb0;
+		usb1 = &usb1;

is this valid?
git grep of_alias_ driver/usb/

am I missing something?

Quoted 19 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +19 -0
+	};
+
+	memory@80000000 {
+		/* 256MB */
+		reg = <0x00000000 0x80000000 0x00000000 0x10000000>;
+		device_type = "memory";
+		bootph-all;
+	};
+
+	thermal-zones {
+		wkup0-thermal {
+			polling-delay-passive = <250>;	/* milliSeconds */
+			polling-delay = <500>;		/* milliSeconds */
+			thermal-sensors = <&vtm0 0>;
+
+			trips {
+				crit0 {
+					temperature = <125000>;
+					hysteresis = <2000>;
Quoted 8 lines

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 59

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +5 -0
+					type = "critical";
+				};
+			};
+		};
+	};

This is better done by having something like arch/arm64/boot/dts/ti/k3-am62l-industrial-thermal.dtsi

I am following what k3-am62l3-evm.dts is doing [0], we moved thermal-zones node to the board file instead of defining in thermal.dtsi

[0] https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/ti/k3-am62l3-evm.dts#L61

Quoted 15 lines

[..]

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 214

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+
+	sensor_3v3: regulator-4 {
+		/* TPS22918DBVR */
+		compatible = "regulator-fixed";
+		regulator-name = "Sensor_3V3";
+		regulator-min-microvolt = <3300000>;
+		regulator-max-microvolt = <3300000>;
+		vin-supply = <&vdd_3v3>;
+		regulator-boot-on;
+		regulator-always-on;

Why sensor supply is always on?

No special reason, I can remove to help with power saving.

Quoted 23 lines
Quoted 20 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +19 -0
+		enable-active-high;
+		gpio = <&wkup_gpio0 1 GPIO_ACTIVE_HIGH>;
+		pinctrl-names = "default";
+		pinctrl-0 = <&sensor_3v3_ena_pins_default>;
+		bootph-all;
+	};
+
+	wlan_en: regulator-5 {
+		compatible = "regulator-fixed";
+		regulator-name = "wlan_en";
+		regulator-min-microvolt = <1800000>;
+		regulator-max-microvolt = <1800000>;
+		enable-active-high;
+		gpios = <&gpio0 51 GPIO_ACTIVE_HIGH>;
+		pinctrl-names = "default";
+		pinctrl-0 = <&wlan_en_pins_default>;
+	};
+};
+

[..]

Quoted 13 lines

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 270

Quoted 11 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +11 -0
+
+	usr_button_pins_default: usr-button-default-pins {
+		pinctrl-single,pins = <
+			AM62LX_IOPAD(0x00a4, PIN_INPUT, 7) /* (H18) GPMC0_AD11.GPIO0_26 */
+			AM62LX_IOPAD(0x01e4, PIN_INPUT, 7) /* (D16) EXT_REFCLK1.GPIO0_104 */
+			AM62LX_IOPAD(0x00c0, PIN_INPUT, 7) /* (N19) GPMC0_ADVn_ALE.GPIO0_32 */
+			AM62LX_IOPAD(0x00e8, PIN_INPUT, 7) /* (L19) GPMC0_CSn1.GPIO0_42 */
+			AM62LX_IOPAD(0x00b8, PIN_INPUT, 7) /* (L21) GPMC0_CLK.GPIO0_31 */
+			AM62LX_IOPAD(0x01c0, PIN_INPUT, 7) /* (B13) UART0_RTSn.GPIO0_95 */
+		>;
+	};

no wakeup from usr buttons?

RTC wakeup node is not in upstream tree, so no, user button wakeup support is not enabled yet.

Quoted 9 lines

[...]

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 572

Quoted 4 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +4 -0
+};
+
+&gpio0 {
+	gpio-line-names ="","","","","","","","","","",									/* 0-9 */

space after that =

Will fix.

Quoted 15 lines

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 584

Quoted 13 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +12 -0
+			 "","","","","","BOOST_5V_ENA","VDD_3V3_SD_ENA","","","",					/* 10-19 */
+			 "","","","","","MCP23S18_RESET","BTN_SELECT","","","",						/* 20-29 */
+			 "","BTN_LEFT","BTN_UP","","LORA_RESET","","","","","",						/* 30-39 */
+			 "FUEL_GAUGE_BATLOW","LORA_RFSW","BTN_DOWN","USB_HUB_RST","MIKROBUS_INT","","","","","",	/* 40-49 */
+			 "","WLAN_EN","","","","","","","","",								/* 50-59 */
+			 "","","","","","","","","","",									/* 60-69 */
+			 "","","","","","","","","","",									/* 70-79 */
+			 "","","","","MIKROBUS_RST","","","","LORA_BUSY","",						/* 80-89 */
+			 "","","","","LORA_DIO","BTN_RIGHT","","","","",						/* 90-99 */
+			 "","","","","BTN_BACK","","","","","",								/* 100-109 */
+			 "","","","","","","","","","",									/* 110-119 */
+			 "","","SD_CD","","","";									/* 120-125 */

Could you keep these under 100 chars?

I could for most of these lines I believe, but it will completely mess up the alignment in comments, If that is fine, I will fix. (:

Quoted 36 lines

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 592

Quoted 9 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +8 -0
+	pinctrl-names = "default";
+	pinctrl-0 = <&gpio0_pins_default>, <&usr_button_pins_default>, <&lora_control_pins_default>;
+	bootph-all;
+	status = "okay";
+};
+
+&wkup_gpio0 {
+	gpio-line-names ="","SENSOR_3V3_ENA","","","","","","";								/* 0-7 */

same

Quoted 24 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +24 -0
+	bootph-all;
+	status = "okay";
+};
+
+&sdhci1 {
+	/* SD/MMC */
+	vmmc-supply = <&vdd_3v3_sd>;
+	disable-wp;
+	cd-gpios = <&gpio0 122 GPIO_ACTIVE_LOW>;
+	cd-debounce-delay-ms = <100>;
+	ti,fails-without-test-cd;
+	pinctrl-names = "default";
+	pinctrl-0 = <&mmc1_pins_default>;
+	bootph-all;
+	status = "okay";
+};
+
+&sdhci2 {
+	vmmc-supply = <&wlan_en>;
+	bus-width = <4>;
+	non-removable;
+	cap-power-off-card;
+	keep-power-in-suspend;
+	pinctrl-names = "default";
Quoted 8 lines

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 621

Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +5 -0
+	pinctrl-0 = <&mmc2_pins_default>;
+	ti,driver-strength-ohm = <50>;
+	ti,fails-without-test-cd;
+	status = "okay";
+};

Why not introduce the sdhci2 and supplies once we get wlan driver in upstream?

I can do that. NP.

~ Judith

...

#7 lore raw

Re: [PATCH v4 2/3] arm64: dts: ti: Add k3-am62l3-beaglebadge

Hi Nishanth,

Quoted 55 lines · Judith Mendez
Quoted 10 lines · Nishanth Menon
Quoted 7 lines · Judith Mendez

BeagleBoard.org BeagleBadge is a compact, affordable open source hardware single board computer based on the Texas Instruments AM62L3 SoC designed for IoT and embedded applications with low power consumption. Expansion is provided over open standards based headers including QWIIC and GPIO interfaces.

https://github.com/beagleboard/BeagleBadge

Why not use https://www.beagleboard.org/boards/beaglebadge ?

Will switch link

Quoted 32 lines
Quoted 32 lines

---
Changelog since v3:
- Add missing newline in commit message
- Drop beagleboard URL
- Drop uneeded header files
- Add boothph flags in wkup_i2c0 & PMC nodes
---
  arch/arm64/boot/dts/ti/Makefile               |   1 + .../boot/dts/ti/k3-am62l3-beaglebadge.dts     | 700 ++++++++++++++++++

  2 files changed, 701 insertions(+)

  create mode 100644 arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts

arch/arm64/boot/dts/ti/Makefile +0 -0
index 5269c9619b65c..4e377ca011cd8 100644
@@ -41,6 +41,7 @@ dtb-$(CONFIG_ARCH_K3) += k3-am62d2-evm.dtb
   # Boards with AM62Lx SoCs

  dtb-$(CONFIG_ARCH_K3) += k3-am62l3-evm.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am62l3-beaglebadge.dtb # Boards with AM62Px SoC dtb-$(CONFIG_ARCH_K3) += k3-am62p5-sk.dtb

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +0 -0
new file mode 100644
index 0000000000000..30fc9c83b1f44
@@ -0,0 +1,700 @@
Quoted 8 lines
Quoted 6 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +5 -0
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * https://www.beagleboard.org/boards/beaglebadge
+ *
+ * Copyright (C) 2026 Texas Instruments Incorporated - https:// 

www.ti.com/

Seeing the tags, I assume no BeagleBoard.org member contributions?

Quoted 38 lines

Not yet ^.^

Quoted 36 lines
Quoted 21 lines

+ */

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +19 -0
+
+/dts-v1/;
+
+#include <dt-bindings/gpio/gpio.h>
+#include <dt-bindings/input/input.h>
+#include <dt-bindings/leds/common.h>
+#include "k3-am62l3.dtsi"
+#include "k3-pinctrl.h"
+
+/ {
+    compatible = "beagle,am62l3-beaglebadge", "ti,am62l3";
+    model = "BeagleBoard.org BeagleBadge";
+
+    chosen {
+        stdout-path = &uart0;
+    };
+
+    aliases {
+        gpio0 = &gpio0;

arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts line 35

Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts new file +10 -0
+        gpio2 = &wkup_gpio0;
+        i2c0 = &i2c0;
+        i2c1 = &i2c1;
+        i2c2 = &i2c2;
+        i2c4 = &wkup_i2c0;
+        mmc1 = &sdhci1;
+        mmc2 = &sdhci2;
+        serial3 = &uart1;
+        usb0 = &usb0;
+        usb1 = &usb1;

is this valid?
git grep of_alias_ driver/usb/

am I missing something?

Missed this one, actually I had originally copied alias list from beagleplay [0], but checking once, seems like these aliases are not needed, so will remove for Badge & beagleplay as well.

~ Judith

...

#8 lore raw

PATCH v4 3/3 arm64: defconfig: Enable drivers for BeagleBadge

In reply to Judith Mendez

Enable drivers used on BeagleBadge[1]:
- LED PWM Multicolor driver as a module
- MCP SPI IO Expander driver as a module
- Seven Segment display GPIO driver as module
- Temperature Sensor driver as a module

[1] https://github.com/beagleboard/BeagleBadge

---
Changelog since v3:
- Add missing newline in commit message

---
 arch/arm64/configs/defconfig | 5 +++++
 1 file changed, 5 insertions(+)
arch/arm64/configs/defconfig +5 -0
index d905a0777f939..5cfb7f6f2ae78 100644
@@ -634,6 +634,7 @@ CONFIG_PINCTRL_BRCMSTB=y
 CONFIG_PINCTRL_BCM2712=y
 CONFIG_PINCTRL_DA9062=m
 CONFIG_PINCTRL_MAX77620=y
+CONFIG_PINCTRL_MCP23S08=m
 CONFIG_PINCTRL_RK805=m
 CONFIG_PINCTRL_SINGLE=y
 CONFIG_PINCTRL_SX150X=m
@@ -766,6 +767,7 @@ CONFIG_SENSORS_LM90=m
 CONFIG_SENSORS_PWM_FAN=m
 CONFIG_SENSORS_RASPBERRYPI_HWMON=m
 CONFIG_SENSORS_SL28CPLD=m
+CONFIG_SENSORS_SHT4x=m
 CONFIG_SENSORS_AMC6821=m
 CONFIG_SENSORS_INA2XX=m
 CONFIG_SENSORS_INA3221=m
@@ -955,6 +957,8 @@ CONFIG_VIDEO_IMX412=m
 CONFIG_VIDEO_OV5640=m
 CONFIG_VIDEO_OV5645=m
 CONFIG_VIDEO_S5KJN1=m
+CONFIG_AUXDISPLAY=y
+CONFIG_SEG_LED_GPIO=m
 CONFIG_DRM=m
 CONFIG_DRM_I2C_NXP_TDA998X=m
 CONFIG_DRM_HDLCD=m
@@ -1332,6 +1336,7 @@ CONFIG_LEDS_GPIO=y
 CONFIG_LEDS_PWM=y
 CONFIG_LEDS_SYSCON=y
 CONFIG_LEDS_QCOM_FLASH=m
+CONFIG_LEDS_PWM_MULTICOLOR=m
 CONFIG_LEDS_QCOM_LPG=m
 CONFIG_LEDS_TRIGGER_TIMER=y
 CONFIG_LEDS_TRIGGER_DISK=y
Signature · 1 line
2.54.0
maintainer
#9 lore raw
In reply to Judith Mendez
Quoted 9 lines · Judith Mendez

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:

in all patches,
Is https://www.beagleboard.org/boards/beaglebadge a better canonical link?

Robert/Jason: for some reason https://www.beagleboard.org/boards does'nt list it. Is there a reason?

Quoted 41 lines

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

Changelog since v3:
- Fix newline in commit messages
- Drop vendor URLs
DTS:
- Add bootph flags in wakup i2c & PMIC nodes for completeness
- Drop unneeded header files

v3

V2

V1

Patch series depends on:

[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     | 700 ++++++++++++++++++
 arch/arm64/configs/defconfig                  |   5 +
 4 files changed, 707 insertions(+)
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts
Signature · 1 line
2.54.0
Signature · 4 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource
#10 lore raw

Hi Nishanth,

Quoted 8 lines · Nishanth Menon
Quoted 7 lines · Judith Mendez

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.

Quoted 6 lines
Quoted 2 lines

SD boot:

in all patches,
Is https://www.beagleboard.org/boards/beaglebadge a better canonical link?

I can switch links, it seems to be working now.

...