mbox series

[v2,0/5] Add Toradex Verdin AM62

Message ID 20230601131332.26877-1-francesco@dolcini.it
Headers show
Series Add Toradex Verdin AM62 | expand

Message

Francesco Dolcini June 1, 2023, 1:13 p.m. UTC
From: Francesco Dolcini <francesco.dolcini@toradex.com>

This series adds support for the Toradex Verdin AM62 SoM which can be used on
different carrier boards (Verdin Development Board, Dahlia and Yavia).

The module consists of an TI AM62 family SoC (either AM623 or AM625), a
TPS65219 PMIC, a Gigabit Ethernet PHY, 512MB to 2GB of LPDDR4 RAM, an eMMC, a
TLA2024 ADC, an I2C EEPROM, an RX8130 RTC, and optional Parallel RGB to MIPI
DSI bridge plus an optional Bluetooth/Wi-Fi module.

Link: https://www.toradex.com/computer-on-modules/verdin-arm-family/ti-am62

v2: 
 - removed spurious new lines
 - removed TODO comment
 - fixed pinctrl format
 - added link to products in dts/dtsi
 - removed useless rs485-rts-active-high property

Francesco Dolcini (5):
  dt-bindings: arm: ti: add toradex,verdin-am62 et al.
  arm64: defconfig: enable drivers for Verdin AM62
  arm64: dts: ti: add verdin am62
  arm64: dts: ti: add verdin am62 dahlia
  arm64: dts: ti: add verdin am62 yavia

 .../devicetree/bindings/arm/ti/k3.yaml        |   20 +
 arch/arm64/boot/dts/ti/Makefile               |    6 +
 .../boot/dts/ti/k3-am62-verdin-dahlia.dtsi    |  219 +++
 .../arm64/boot/dts/ti/k3-am62-verdin-dev.dtsi |  240 +++
 .../boot/dts/ti/k3-am62-verdin-nonwifi.dtsi   |   20 +
 .../boot/dts/ti/k3-am62-verdin-wifi.dtsi      |   39 +
 .../boot/dts/ti/k3-am62-verdin-yavia.dtsi     |  207 +++
 arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi    | 1401 +++++++++++++++++
 .../dts/ti/k3-am625-verdin-nonwifi-dahlia.dts |   22 +
 .../dts/ti/k3-am625-verdin-nonwifi-dev.dts    |   22 +
 .../dts/ti/k3-am625-verdin-nonwifi-yavia.dts  |   22 +
 .../dts/ti/k3-am625-verdin-wifi-dahlia.dts    |   22 +
 .../boot/dts/ti/k3-am625-verdin-wifi-dev.dts  |   22 +
 .../dts/ti/k3-am625-verdin-wifi-yavia.dts     |   22 +
 arch/arm64/configs/defconfig                  |    3 +
 15 files changed, 2287 insertions(+)
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62-verdin-dahlia.dtsi
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62-verdin-dev.dtsi
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62-verdin-nonwifi.dtsi
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62-verdin-wifi.dtsi
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62-verdin-yavia.dtsi
 create mode 100644 arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi
 create mode 100644 arch/arm64/boot/dts/ti/k3-am625-verdin-nonwifi-dahlia.dts
 create mode 100644 arch/arm64/boot/dts/ti/k3-am625-verdin-nonwifi-dev.dts
 create mode 100644 arch/arm64/boot/dts/ti/k3-am625-verdin-nonwifi-yavia.dts
 create mode 100644 arch/arm64/boot/dts/ti/k3-am625-verdin-wifi-dahlia.dts
 create mode 100644 arch/arm64/boot/dts/ti/k3-am625-verdin-wifi-dev.dts
 create mode 100644 arch/arm64/boot/dts/ti/k3-am625-verdin-wifi-yavia.dts

Comments

Tony Lindgren June 2, 2023, 7:20 a.m. UTC | #1
Hi,

* Francesco Dolcini <francesco@dolcini.it> [230601 13:15]:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
> 
> Add toradex,verdin-am62 for Toradex Verdin AM62 SoM, its
> nonwifi and wifi variants and the carrier boards (Dahlia,
> Verdin Development Board and Yavia) they may be mated in.

Looks like you have wifi on sdio, there should be no need for separate
compatible properties. The sdio wifi will try to probe and will just bail
out if no wifi is populated.

If however the non-wifi variants are recycling the sdio pins for something
else, then it's it's a different story. In that case you want either
seprate compatible properties, or want to use dts fragments possibly.

Regards,

Tony
Francesco Dolcini June 2, 2023, 8:18 a.m. UTC | #2
On Fri, Jun 02, 2023 at 10:20:45AM +0300, Tony Lindgren wrote:
> Hi,
> 
> * Francesco Dolcini <francesco@dolcini.it> [230601 13:15]:
> > From: Francesco Dolcini <francesco.dolcini@toradex.com>
> > 
> > Add toradex,verdin-am62 for Toradex Verdin AM62 SoM, its
> > nonwifi and wifi variants and the carrier boards (Dahlia,
> > Verdin Development Board and Yavia) they may be mated in.
> 
> Looks like you have wifi on sdio, there should be no need for separate
> compatible properties. The sdio wifi will try to probe and will just bail
> out if no wifi is populated.
> 
> If however the non-wifi variants are recycling the sdio pins for something
> else, then it's it's a different story. In that case you want either
> seprate compatible properties, or want to use dts fragments possibly.

This is exactly the case, the wifi/non-wifi variant are re-using pins.

I provided a more verbose explanation on that on a previous discussion
https://lore.kernel.org/all/ZG5jYV%2FNfGJvYkma@francesco-nb.int.toradex.com/

Francesco