dt-bindings: arm: ti: Add PocketBeagle2

This board is based on ti,am625 family using the am6232 and am6254 variations.

https://www.beagleboard.org/boards/pocketbeagle-2
https://openbeagle.org/pocketbeagle/pocketbeagle-2

---
Changes since v2:
- Apply Reviewed-by from Dhruva Gole
Changes since v1:
- Apply acked-by from Conor Dooley

---
 Documentation/devicetree/bindings/arm/ti/k3.yaml | 1 +
 1 file changed, 1 insertion(+)

index 18f155cd06c8..b7f6cd8d4b9e 100644
@@ -46,6 +46,7 @@ properties:
       - description: K3 AM625 SoC
         items:
           - enum:
+              - beagle,am62-pocketbeagle2
               - beagle,am625-beagleplay
               - ti,am625-sk
               - ti,am62-lp-sk

2.47.2

BeagleBoard.org PocketBeagle 2 is an upgraded version of the popular PocketBeagle. It is based on Texas Instruments AM6232 or AM6254 SoC. Its dual or quad A53 cores can provide higher performance than classic PocketBeagle. The new design comes with pre-soldered headers, a 3-pin JST-SH 1.00mm UART debug port, a USB-C port, Texas Instruments MSPM0L1105 Cortex-M0+ MCU for ADC, 512MB RAM, and a LiPo Battery charger.

MSPM0L1105 firmware source: https://openbeagle.org/pocketbeagle/mspm0-adc-eeprom
* EEPROM 24c32 emulation
* ADC ad7291 emulation

https://www.beagleboard.org/boards/pocketbeagle-2
https://openbeagle.org/pocketbeagle/pocketbeagle-2

---
Changes since v2:
- cleanup unused serial aliases
- cleanup unused sdhci0 (un-populated) aliases
- cleanup unused main_i2c1 (un-populated) aliases
- add missing main_i2c0 aliases
- fix bootph, function, color, gpios order in leds nodes
- drop local cpsw disable, needs to be moved to k3-am62-main
- MSPM0L1105 add firmware source and note where emulated
- usb0 add note about Type-C connector, but only wired for USB 2.0
- usb1 add compatible note with original PocketBeagle expansion boards
Changes since v1:
- fix '_' in main-i2c2-default-pins
- aliases i2c match original pocketbeagle
- add mcu_m4fss with reseved memory and mailbox
- drop unused main_gpio0_pins_default pinmux
- drop unused main_gpio1_pins_default pinmux
- drop unused main_spi2_pins_gpio pinmux
- Reserve 128MiB of global CMA

---
 arch/arm64/boot/dts/ti/Makefile               |   1 +
 .../boot/dts/ti/k3-am62-pocketbeagle2.dts     | 518 ++++++++++++++++++
 2 files changed, 519 insertions(+)
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62-pocketbeagle2.dts

index 03d4cecfc001..4f8fcb69a2c1 100644
@@ -27,6 +27,7 @@ dtb-$(CONFIG_ARCH_K3) += k3-am625-verdin-wifi-yavia.dtb
 dtb-$(CONFIG_ARCH_K3) += k3-am62x-phyboard-lyra-gpio-fan.dtbo
 dtb-$(CONFIG_ARCH_K3) += k3-am62-lp-sk.dtb
 dtb-$(CONFIG_ARCH_K3) += k3-am62-lp-sk-nand.dtbo
+dtb-$(CONFIG_ARCH_K3) += k3-am62-pocketbeagle2.dtb
 
 # Boards with AM62Ax SoC
 dtb-$(CONFIG_ARCH_K3) += k3-am62a7-sk.dtb

2.47.2

On April 15, 2025 thus sayeth Robert Nelson:

I must say this is a fun little board! Excited to see all the carrier boards people will make :)

~Bryan

Hi,

Thanks for all the fixes, I also boot tested with a bare minimum Image [1]

[1]
https://gist.github.com/DhruvaG2000/d67dce191b6613736ba38f19cf0a0cc6
[No modules installed, only kernel + DTB boot test]

Best regards,
Dhruva Gole
Texas Instruments Incorporated

Please drop the autogenerated scripts/get_maintainer.pl CC-entries from commit msg. There is no single need to store automated output of get_maintainers.pl in the git log. It can be easily re-created at any given time, thus its presence in the git history is redundant and obfuscates the log.

If you need it for your own patch management purposes, keep it under the --- separator.

Best regards,
Krzysztof

Hi Robert Nelson,

I have applied the following to branch ti-k3-dts-next on [1].

I have dropped the Cc list as Krystoff pointed out this time around when I applies the patch, but, please take care of this from the next series on.

Thank you!

[1/2] dt-bindings: arm: ti: Add PocketBeagle2

      commit: 3a5ff313ac521ff034f07ea6687ffb3f2229d62a
[2/2] arm64: dts: ti: Add k3-am62-pocketbeagle2
      commit: 92d8c028aa924286f10ac75b7f9e8edfc9ed432b

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git

Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D