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

[Andrew Davis]

On 5/5/26 10:48 AM, Judith Mendez wrote:
> Hi Bryan, all,
> 
> On 5/4/26 11:19 AM, Bryan Brattlof wrote:
>> On May  1, 2026 thus sayeth 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://beagleboard.org/
>>> https://github.com/beagleboard/BeagleBadge
>>>
>>> Co-developed-by: Andrew Davis <afd at ti.com>
>>> Signed-off-by: Judith Mendez <jm at ti.com>
>>> ---
>>>   arch/arm64/boot/dts/ti/Makefile            |   1 +
>>>   arch/arm64/boot/dts/ti/k3-am62l3-badge.dts | 655 +++++++++++++++++++++
>>
>> ...
>>
>>> diff --git a/arch/arm64/boot/dts/ti/k3-am62l3-badge.dts
>>> b/arch/arm64/boot/dts/ti/k3-am62l3-badge.dts
>>> new file mode 100644
>>> index 000000000000..0125d3fec5e9
>>> --- /dev/null
>>> +++ b/arch/arm64/boot/dts/ti/k3-am62l3-badge.dts
>>> @@ -0,0 +1,655 @@
>>> +// SPDX-License-Identifier: GPL-2.0
>>> +/*
>>> + * https://www.beagleboard.org/boards/beaglebadge
>>> + *
>>> + * Copyright (C) 2026 Texas Instruments Incorporated - https://www.ti.com/
>>> + */
>>> +
>>> +/dts-v1/;
>>> +
>>> +#include <dt-bindings/gpio/gpio.h>
>>> +#include <dt-bindings/input/input.h>
>>> +#include <dt-bindings/leds/common.h>
>>> +#include <dt-bindings/net/ti-dp83867.h>
>>> +#include "k3-am62l3.dtsi"
>>> +#include "k3-pinctrl.h"
>>> +
>>> +/ {
>>> +    compatible = "beagle,am62l3-badge", "ti,am62l3";
>>
>> I noticed the $subject calls it the k3-am62l3-beaglebadge do we want to
>> name the DT that as well?
>>
>>> +    model = "BeagleBoard.org BeagleBadge";
>>> +
>>
> 
> So I see other beagle boards have the following:
> 
> beagle,am67a-beagley-ai in k3-am67a-beagley-ai.dts
> beagle,am625-beagleplay in k3-am625-beagleplay.dts
> beagle,am62-pocketbeagle2 in k3-am62-pocketbeagle2.dts
> beagle,j721e-beagleboneai64 in k3-j721e-beagleboneai64.dts
> 
> so I think we should be using:
> 
> beagle,am62l3-beaglebadge in k3-am62l3-beaglebadge.dts
> 
> so if it is fine with everyone will update compatible
> & DT filename accordingly.
> 

Looks correct to me.

>>
>>> +&sdhci2 {
>>> +    vmmc-supply = <&wlan_en>;
>>> +    bus-width = <4>;
>>> +    non-removable;
>>> +    cap-power-off-card;
>>> +    keep-power-in-suspend;
>>> +    #address-cells = <1>;
>>> +    #size-cells = <0>;
>>> +    pinctrl-names = "default";
>>> +    pinctrl-0 = <&mmc2_pins_default>;
>>> +    ti,driver-strength-ohm = <50>;
>>> +    ti,fails-without-test-cd;
>>> +    status = "okay";
>>> +
>>> +    wlcore: wlcore at 2 {
>>> +        compatible = "ti,cc3300";
>>
>> Sadly this only exists on our evil vendor tree :/
> 
> So sure, I saw that the WIFI driver is not in mainline,
> but I also referenced beagleplay series & it seems
> like as long as the hardware is described properly,
> the node can be upstreamed. Please correct me if I
> am wrong here..
> 

Only in some special cases, but in general the driver needs
to be upstreamed first. And even in those special cases a
DT binding is always needed first. Otherwise how would we know
if the node is described properly.

For Beagleplay I only see the CC1352P7 radio in DT upstream,
and it has a proper binding[0]. For now drop the CC3300, we
can simply add it when the driver gets upstream.

Andrew

[0] Documentation/devicetree/bindings/net/ti,cc1352p7.yaml

>>
>>> +        reg = <2>;
>>> +        interrupt-parent = <&gpio0>;
>>> +        interrupts = <52 IRQ_TYPE_EDGE_RISING>;
>>> +        pinctrl-names = "default";
>>> +        pinctrl-0 = <&wlirq_pins_default>;
>>> +    };
>>> +};
>>> +
>>
>> Scanning over the bootlog it looks like the VTM driver is active but
>> we're missing the thermal-zones{} node which is causing it issues.
> 
> Opps, will add. thanks.
> 
> ~ judith