Initial Kontron SMARC-sAM67 support
Subsystems (2)
v3 cover Initial Kontron SMARC-sAM67 support
This series contains the remaining (device tree) patches for the Kontron SMARC-sAM67 module.
v3:
- dropped all patches which were already applied
- add 'bootph-all' to the usb ctrl node to support DFU boot
- as all MFD bits are now merged, combine the patch which added the system controller node into the main one again
- drop duplicate RTC node. This one was a left over before the rtc node moved into it's own overlay
- add a new overlay for the Kontron SMARC 2.2 evaluation carrier
- add a new SMARC gpio overlay to configure the pinmux correct. This is not integrated into the default device tree because it will conflict with any device tree which will use the pins for different purposes (they are multi function pins)
v2:
- dropped patches which were already picked up
- new patch "dt-bindings: mfd: tps6594: allow gpio-line-names"
- separate driver for the hwmon, add missing hwmon documentation, thanks Guenter
- split the DT as suggested by the SoC maintainers
- add missing copyright and license to the overlays, thanks Andrew
Michael Walle (3):
dt-bindings: arm: ti: Add Kontron SMARC-sAM67 module
arm64: dts: ti: Add support for Kontron SMARC-sAM67
arm64: dts: ti: sa67: add overlay for the ADS2 carrier
.../devicetree/bindings/arm/ti/k3.yaml | 1 + arch/arm64/boot/dts/ti/Makefile | 10 + .../dts/ti/k3-am67a-kontron-sa67-ads2.dtso | 146 +++ .../dts/ti/k3-am67a-kontron-sa67-base.dts | 1091 +++++++++++++++++ .../dts/ti/k3-am67a-kontron-sa67-gbe1.dtso | 26 + .../dts/ti/k3-am67a-kontron-sa67-gpios.dtso | 61 + .../ti/k3-am67a-kontron-sa67-rtc-rv8263.dtso | 31 + 7 files changed, 1366 insertions(+) create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-ads2.dtso create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gbe1.dtso create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gpios.dtso create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-rtc-rv8263.dtso
Signature · 1 line
2.47.3
PATCH v3 1/3 dt-bindings: arm: ti: Add Kontron SMARC-sAM67 module
Add devicetree bindings for the AM67 based Kontron SMARC-sAM67 module.
--- Documentation/devicetree/bindings/arm/ti/k3.yaml | 1 + 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/arm/ti/k3.yaml +1 -0
@@ -194,6 +194,7 @@ properties: items: - enum: - beagle,am67a-beagley-ai + - kontron,sa67 # Kontron SMARC-sAM67 board - ti,j722s-evm - const: ti,j722s
Signature · 1 line
2.47.3
PATCH v3 2/3 arm64: dts: ti: Add support for Kontron SMARC-sAM67
In reply to Michael WalleAdd device tree support for the Kontron SMARC-sAM67 module, which is based on a TI AM67A SoC.
The module features:
* Quad-core AM67A94 at 1.4GHz with 8 GiB RAM
* 64 GiB eMMC, 4 MiB SPI flash for failsafe booting
* Dedicated RTC
* Multiple interfaces: 4x UART, 2x USB 2.0/USB 3.2, 2x GBE, QSPI,
7x I2C,
* Display support: 2x LVDS, 1x DSI (*), 1x DP (*)
* Camera support: 4x CSI (*)
* Onboard microcontroller for boot control, failsafe booting and external watchdog
(*) not yet supported by the kernel
There is a base device tree and overlays which will add optional features. At the moment there is one full featured variant of that board whose device tree is generated during build by merging all the device tree overlays.
--- arch/arm64/boot/dts/ti/Makefile | 7 + .../dts/ti/k3-am67a-kontron-sa67-base.dts | 1091 +++++++++++++++++ .../dts/ti/k3-am67a-kontron-sa67-gbe1.dtso | 26 + .../dts/ti/k3-am67a-kontron-sa67-gpios.dtso | 61 + .../ti/k3-am67a-kontron-sa67-rtc-rv8263.dtso | 31 + 5 files changed, 1216 insertions(+) create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gbe1.dtso create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gpios.dtso create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-rtc-rv8263.dtso
arch/arm64/boot/dts/ti/Makefile +7 -0
@@ -137,7 +137,14 @@ dtb-$(CONFIG_ARCH_K3) += k3-j721s2-evm-pcie1-ep.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j721s2-evm-usb0-type-a.dtbo # Boards with J722s SoC +k3-am67a-kontron-sa67-dtbs := k3-am67a-kontron-sa67-base.dtb \ + k3-am67a-kontron-sa67-rtc-rv8263.dtbo k3-am67a-kontron-sa67-gbe1.dtbo dtb-$(CONFIG_ARCH_K3) += k3-am67a-beagley-ai.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-base.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-gbe1.dtbo +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-gpios.dtbo +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-rtc-rv8263.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm.dtb dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm-csi2-quad-tevi-ov5640.dtbo
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +1091 -0
1,091 lines not on this page · raw message
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gbe1.dtso new file +26 -0
@@ -0,0 +1,26 @@ +// SPDX-License-Identifier: GPL-2.0-only OR MIT +/* + * Second ethernet port GBE1. + * + * Copyright (c) 2025 Kontron Europe GmbH + */ + +/dts-v1/; +/plugin/; + +&cpsw3g_mdio { + #address-cells = <1>; + #size-cells = <0>; + + phy1: ethernet-phy@1 { + reg = <1>; + }; +}; + +&cpsw_port2 { + phy-connection-type = "rgmii-id"; + phy-handle = <&phy1>; + nvmem-cells = <&base_mac_address 1>; + nvmem-cell-names = "mac-address"; + status = "okay"; +};
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gpios.dtso new file +61 -0
61 lines not on this page · raw message
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-rtc-rv8263.dtso new file +31 -0
@@ -0,0 +1,31 @@ +// SPDX-License-Identifier: GPL-2.0-only OR MIT +/* + * Microcrystal RV8263 RTC variant. + * + * Copyright (c) 2025 Kontron Europe GmbH + */ + +/dts-v1/; +/plugin/; + +#include <dt-bindings/interrupt-controller/irq.h> + +&{/} { + aliases { + rtc0 = "/bus@f0000/i2c@20000000/rtc@51"; /* &rtc */ + rtc1 = "/bus@f0000/bus@b00000/rtc@2b1f0000"; /* &wkup_rtc0 */ + }; +}; + +&main_i2c0 { + #address-cells = <1>; + #size-cells = <0>; + + rtc: rtc@51 { + compatible = "microcrystal,rv8263"; + reg = <0x51>; + pinctrl-names = "default"; + pinctrl-0 = <&rtc_pins_default>; + interrupts-extended = <&main_gpio0 36 IRQ_TYPE_EDGE_FALLING>; + }; +};
Signature · 1 line
2.47.3
Re: [PATCH v3 2/3] arm64: dts: ti: Add support for Kontron SMARC-sAM67
Hi Michael
Quoted 75 lines · Michael Walle
Add device tree support for the Kontron SMARC-sAM67 module, which is based on a TI AM67A SoC.
The module features:
* Quad-core AM67A94 at 1.4GHz with 8 GiB RAM
* 64 GiB eMMC, 4 MiB SPI flash for failsafe booting
* Dedicated RTC
* Multiple interfaces: 4x UART, 2x USB 2.0/USB 3.2, 2x GBE, QSPI,7x I2C,* Display support: 2x LVDS, 1x DSI (*), 1x DP (*)
* Camera support: 4x CSI (*)
* Onboard microcontroller for boot control, failsafe booting and external watchdog(*) not yet supported by the kernel
There is a base device tree and overlays which will add optional features. At the moment there is one full featured variant of that board whose device tree is generated during build by merging all the device tree overlays.
Signed-off-by Michael Walle <[email protected]>--- arch/arm64/boot/dts/ti/Makefile | 7 + .../dts/ti/k3-am67a-kontron-sa67-base.dts | 1091 +++++++++++++++++ .../dts/ti/k3-am67a-kontron-sa67-gbe1.dtso | 26 + .../dts/ti/k3-am67a-kontron-sa67-gpios.dtso | 61 + .../ti/k3-am67a-kontron-sa67-rtc-rv8263.dtso | 31 + 5 files changed, 1216 insertions(+)create mode 100644
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dtscreate mode 100644arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gbe1.dtsocreate mode 100644arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gpios.dtsocreate mode 100644arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-rtc-rv8263.dtsoarch/arm64/boot/dts/ti/Makefile +7
-0@@ -137,7 +137,14 @@ dtb-$(CONFIG_ARCH_K3) += k3-j721s2-evm-pcie1-ep.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j721s2-evm-usb0-type-a.dtbo # Boards with J722s SoC +k3-am67a-kontron-sa67-dtbs := k3-am67a-kontron-sa67-base.dtb \ + k3-am67a-kontron-sa67-rtc-rv8263.dtbo k3-am67a-kontron-sa67-gbe1.dtbo dtb-$(CONFIG_ARCH_K3) += k3-am67a-beagley-ai.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-base.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-gbe1.dtbo +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-gpios.dtbo +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-rtc-rv8263.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm.dtb dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm-csi2-quad-tevi-ov5640.dtboarch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +15
-0@@ -0,0 +1,1091 @@ +// SPDX-License-Identifier: GPL-2.0-only OR MIT +/* + * Kontron SMARC-sAM67 module + * + * Copyright (c) 2025 Kontron Europe GmbH + */ + +/dts-v1/; + +#include <dt-bindings/gpio/gpio.h> +#include <dt-bindings/interrupt-controller/irq.h> +#include <dt-bindings/phy/phy.h> +#include "k3-j722s.dtsi" +#include "k3-serdes.h" +[..]+
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts line 643
Quoted 6 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +6
-0+ ospi0_pins_default: ospi0-default-pins { + pinctrl-single,pins = < + J722S_IOPAD(0x000, PIN_OUTPUT, 0) /* (L24) OSPI0_CLK */ + J722S_IOPAD(0x02c, PIN_OUTPUT, 0) /* (K26) OSPI0_CSn0 */ + J722S_IOPAD(0x030, PIN_OUTPUT, 0) /* (K23) OSPI0_CSn1 */ + J722S_IOPAD(0x034, PIN_OUTPUT, 0) /* (K22) OSPI0_CSn2 */
I am not sure, which flash device is being used , could you check once if all three CS are supported.
Quoted 18 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +18
-0+ J722S_IOPAD(0x00c, PIN_INPUT, 0) /* (K27) OSPI0_D0 */ + J722S_IOPAD(0x010, PIN_INPUT, 0) /* (L27) OSPI0_D1 */ + J722S_IOPAD(0x014, PIN_INPUT, 0) /* (L26) OSPI0_D2 */ + J722S_IOPAD(0x018, PIN_INPUT, 0) /* (L25) OSPI0_D3 */ + >; + bootph-all; + }; + + pcie0_rc_pins_default: pcie0-rc-default-pins { + pinctrl-single,pins = < + J722S_IOPAD(0x2ac, PIN_OUTPUT, 0) /* (F25) PCIE0_CLKREQn */ + J722S_IOPAD(0x1b4, PIN_OUTPUT, 7) /* (B20) SPI0_CS0.GPIO1_15 */ + >; + }; + + pmic_irq_pins_default: pmic-irq-default-pins { + pinctrl-single,pins = < + J722S_IOPAD(0x090, PIN_INPUT, 7) /* (P27) GPMC0_BE0n_CLE.GPIO0_35 */
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts
Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +9
-0+ >; + }; + +/* I2C_PM */ +&wkup_i2c0 { + pinctrl-names = "default"; + pinctrl-0 = <&wkup_i2c0_pins_default>; + clock-frequency = <100000>; + status = "okay";
This is more a question, I see all i2c controller you want to run at 100Kz, but most of devices are supporting 400Khz
like tps652g1 over main_i2c0 , pca9546 over main_i2c1 , is there specific reason for this
Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +10
-0+}; + +/* SER3 */ +&wkup_uart0 { + /* WKUP UART0 is used by Device Manager firmware */ + pinctrl-names = "default"; + pinctrl-0 = <&wkup_uart0_pins_default>; + bootph-all; + status = "reserved"; +};
[..]
Re: [PATCH v3 2/3] arm64: dts: ti: Add support for Kontron SMARC-sAM67
Hi Udit,
thanks for the thorough review!
Quoted 77 lines · Udit Kumar
Quoted 76 lines · Michael Walle
Add device tree support for the Kontron SMARC-sAM67 module, which is based on a TI AM67A SoC.
The module features:
* Quad-core AM67A94 at 1.4GHz with 8 GiB RAM
* 64 GiB eMMC, 4 MiB SPI flash for failsafe booting
* Dedicated RTC
* Multiple interfaces: 4x UART, 2x USB 2.0/USB 3.2, 2x GBE, QSPI,7x I2C,* Display support: 2x LVDS, 1x DSI (*), 1x DP (*)
* Camera support: 4x CSI (*)
* Onboard microcontroller for boot control, failsafe booting and external watchdog(*) not yet supported by the kernel
There is a base device tree and overlays which will add optional features. At the moment there is one full featured variant of that board whose device tree is generated during build by merging all the device tree overlays.
Signed-off-by Michael Walle <[email protected]>--- arch/arm64/boot/dts/ti/Makefile | 7 + .../dts/ti/k3-am67a-kontron-sa67-base.dts | 1091 +++++++++++++++++ .../dts/ti/k3-am67a-kontron-sa67-gbe1.dtso | 26 + .../dts/ti/k3-am67a-kontron-sa67-gpios.dtso | 61 + .../ti/k3-am67a-kontron-sa67-rtc-rv8263.dtso | 31 + 5 files changed, 1216 insertions(+)create mode 100644
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dtscreate mode 100644arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gbe1.dtsocreate mode 100644arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gpios.dtsocreate mode 100644arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-rtc-rv8263.dtsoarch/arm64/boot/dts/ti/Makefile +7
-0@@ -137,7 +137,14 @@ dtb-$(CONFIG_ARCH_K3) += k3-j721s2-evm-pcie1-ep.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j721s2-evm-usb0-type-a.dtbo # Boards with J722s SoC +k3-am67a-kontron-sa67-dtbs := k3-am67a-kontron-sa67-base.dtb \ + k3-am67a-kontron-sa67-rtc-rv8263.dtbo k3-am67a-kontron-sa67-gbe1.dtbo dtb-$(CONFIG_ARCH_K3) += k3-am67a-beagley-ai.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-base.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-gbe1.dtbo +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-gpios.dtbo +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-rtc-rv8263.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm.dtb dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm-csi2-quad-tevi-ov5640.dtboarch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +15
-0@@ -0,0 +1,1091 @@ +// SPDX-License-Identifier: GPL-2.0-only OR MIT +/* + * Kontron SMARC-sAM67 module + * + * Copyright (c) 2025 Kontron Europe GmbH + */ + +/dts-v1/; + +#include <dt-bindings/gpio/gpio.h> +#include <dt-bindings/interrupt-controller/irq.h> +#include <dt-bindings/phy/phy.h> +#include "k3-j722s.dtsi" +#include "k3-serdes.h" +[..]+
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +1
-0+ ospi0_pins_default: ospi0-default-pins {
Quoted 8 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts line 643
Quoted 5 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +5
-0+ pinctrl-single,pins = < + J722S_IOPAD(0x000, PIN_OUTPUT, 0) /* (L24) OSPI0_CLK */ + J722S_IOPAD(0x02c, PIN_OUTPUT, 0) /* (K26) OSPI0_CSn0 */ + J722S_IOPAD(0x030, PIN_OUTPUT, 0) /* (K23) OSPI0_CSn1 */ + J722S_IOPAD(0x034, PIN_OUTPUT, 0) /* (K22) OSPI0_CSn2 */I am not sure, which flash device is being used , could you check once if all three CS are supported.
Yes, all three are used. This board has one 4MiB on-board flash W25Q32 (or similar) and the two others CS are routed to the edge connector. They aren't multi purpose, so we can already set them to the CS function.
Quoted 33 lines
Quoted 18 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +18
-0+ J722S_IOPAD(0x00c, PIN_INPUT, 0) /* (K27) OSPI0_D0 */ + J722S_IOPAD(0x010, PIN_INPUT, 0) /* (L27) OSPI0_D1 */ + J722S_IOPAD(0x014, PIN_INPUT, 0) /* (L26) OSPI0_D2 */ + J722S_IOPAD(0x018, PIN_INPUT, 0) /* (L25) OSPI0_D3 */ + >; + bootph-all; + }; + + pcie0_rc_pins_default: pcie0-rc-default-pins { + pinctrl-single,pins = < + J722S_IOPAD(0x2ac, PIN_OUTPUT, 0) /* (F25) PCIE0_CLKREQn */ + J722S_IOPAD(0x1b4, PIN_OUTPUT, 7) /* (B20) SPI0_CS0.GPIO1_15 */ + >; + }; + + pmic_irq_pins_default: pmic-irq-default-pins { + pinctrl-single,pins = < + J722S_IOPAD(0x090, PIN_INPUT, 7) /* (P27) GPMC0_BE0n_CLE.GPIO0_35 */arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts
Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +9
-0+ >; + }; + +/* I2C_PM */ +&wkup_i2c0 { + pinctrl-names = "default"; + pinctrl-0 = <&wkup_i2c0_pins_default>; + clock-frequency = <100000>; + status = "okay";This is more a question, I see all i2c controller you want to run at 100Kz, but most of devices are supporting 400Khz
Quoted 2 lines
like tps652g1 over
main_i2c0, pca9546 overmain_i2c1, is there specific reason for this
Actually yes and it was at 400kHz at first. But it wont work with the onboard management controller at that bus. Although it supports 400kHz, the mode in which we are using it, doesn't. In short, we aren't using clock stretching as this might cause the whole bus to hang without being able to recover it from the SoC. Therefore, the i2c reply bytes have to be prepared just-in-time and it turn out that 400kHz is too fast for that.
-michael
Quoted 11 lines
Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +10
-0+}; + +/* SER3 */ +&wkup_uart0 { + /* WKUP UART0 is used by Device Manager firmware */ + pinctrl-names = "default"; + pinctrl-0 = <&wkup_uart0_pins_default>; + bootph-all; + status = "reserved"; +};[..]
Kumar, Udit
Reviewed-byRe: [PATCH v3 2/3] arm64: dts: ti: Add support for Kontron SMARC-sAM67
Hi Michael,
Quoted 89 lines · Michael Walle
Hi Udit,
thanks for the thorough review!
Quoted 76 lines · Udit Kumar
Quoted 75 lines · Michael Walle
Add device tree support for the Kontron SMARC-sAM67 module, which is based on a TI AM67A SoC.
The module features:
* Quad-core AM67A94 at 1.4GHz with 8 GiB RAM
* 64 GiB eMMC, 4 MiB SPI flash for failsafe booting
* Dedicated RTC
* Multiple interfaces: 4x UART, 2x USB 2.0/USB 3.2, 2x GBE, QSPI,7x I2C,* Display support: 2x LVDS, 1x DSI (*), 1x DP (*)
* Camera support: 4x CSI (*)
* Onboard microcontroller for boot control, failsafe booting and external watchdog(*) not yet supported by the kernel
There is a base device tree and overlays which will add optional features. At the moment there is one full featured variant of that board whose device tree is generated during build by merging all the device tree overlays.
Signed-off-by Michael Walle <[email protected]>--- arch/arm64/boot/dts/ti/Makefile | 7 + .../dts/ti/k3-am67a-kontron-sa67-base.dts | 1091 +++++++++++++++++ .../dts/ti/k3-am67a-kontron-sa67-gbe1.dtso | 26 + .../dts/ti/k3-am67a-kontron-sa67-gpios.dtso | 61 + .../ti/k3-am67a-kontron-sa67-rtc-rv8263.dtso | 31 + 5 files changed, 1216 insertions(+)create mode 100644
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dtscreate mode 100644arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gbe1.dtsocreate mode 100644arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gpios.dtsocreate mode 100644arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-rtc-rv8263.dtsoarch/arm64/boot/dts/ti/Makefile +7
-0@@ -137,7 +137,14 @@ dtb-$(CONFIG_ARCH_K3) += k3-j721s2-evm-pcie1-ep.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j721s2-evm-usb0-type-a.dtbo # Boards with J722s SoC +k3-am67a-kontron-sa67-dtbs := k3-am67a-kontron-sa67-base.dtb \ + k3-am67a-kontron-sa67-rtc-rv8263.dtbo k3-am67a-kontron-sa67-gbe1.dtbo dtb-$(CONFIG_ARCH_K3) += k3-am67a-beagley-ai.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-base.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-gbe1.dtbo +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-gpios.dtbo +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-rtc-rv8263.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm.dtb dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm-csi2-quad-tevi-ov5640.dtboarch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +15
-0@@ -0,0 +1,1091 @@ +// SPDX-License-Identifier: GPL-2.0-only OR MIT +/* + * Kontron SMARC-sAM67 module + * + * Copyright (c) 2025 Kontron Europe GmbH + */ + +/dts-v1/; + +#include <dt-bindings/gpio/gpio.h> +#include <dt-bindings/interrupt-controller/irq.h> +#include <dt-bindings/phy/phy.h> +#include "k3-j722s.dtsi" +#include "k3-serdes.h" +[..]+
Quoted 8 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts line 643
Quoted 6 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +6
-0+ ospi0_pins_default: ospi0-default-pins { + pinctrl-single,pins = < + J722S_IOPAD(0x000, PIN_OUTPUT, 0) /* (L24) OSPI0_CLK */ + J722S_IOPAD(0x02c, PIN_OUTPUT, 0) /* (K26) OSPI0_CSn0 */ + J722S_IOPAD(0x030, PIN_OUTPUT, 0) /* (K23) OSPI0_CSn1 */ + J722S_IOPAD(0x034, PIN_OUTPUT, 0) /* (K22) OSPI0_CSn2 */I am not sure, which flash device is being used , could you check once if all three CS are supported.
Quoted 4 lines
Yes, all three are used. This board has one 4MiB on-board flash W25Q32 (or similar) and the two others CS are routed to the edge connector. They aren't multi purpose, so we can already set them to the CS function.
Thanks for details. Just want to make sure, pins are not used for multi purpose.
Please use
Quoted 35 lines
Quoted 33 lines
Quoted 19 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +18
-0+ J722S_IOPAD(0x00c, PIN_INPUT, 0) /* (K27) OSPI0_D0 */ + J722S_IOPAD(0x010, PIN_INPUT, 0) /* (L27) OSPI0_D1 */ + J722S_IOPAD(0x014, PIN_INPUT, 0) /* (L26) OSPI0_D2 */ + J722S_IOPAD(0x018, PIN_INPUT, 0) /* (L25) OSPI0_D3 */ + >; + bootph-all; + }; + + pcie0_rc_pins_default: pcie0-rc-default-pins { + pinctrl-single,pins = < + J722S_IOPAD(0x2ac, PIN_OUTPUT, 0) /* (F25) PCIE0_CLKREQn */ + J722S_IOPAD(0x1b4, PIN_OUTPUT, 7) /* (B20) SPI0_CS0.GPIO1_15 */ + >; + }; + + pmic_irq_pins_default: pmic-irq-default-pins { + pinctrl-single,pins = < + J722S_IOPAD(0x090, PIN_INPUT, 7) /* (P27) GPMC0_BE0n_CLE.GPIO0_35 */arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts
Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +9
-0+ >; + }; + +/* I2C_PM */ +&wkup_i2c0 { + pinctrl-names = "default"; + pinctrl-0 = <&wkup_i2c0_pins_default>; + clock-frequency = <100000>; + status = "okay";This is more a question, I see all i2c controller you want to run at 100Kz, but most of devices are supporting 400Khz
Quoted 2 lines
like tps652g1 over
main_i2c0, pca9546 overmain_i2c1, is there specific reason for this
Quoted 7 lines
Actually yes and it was at 400kHz at first. But it wont work with the onboard management controller at that bus. Although it supports 400kHz, the mode in which we are using it, doesn't. In short, we aren't using clock stretching as this might cause the whole bus to hang without being able to recover it from the SoC. Therefore, the i2c reply bytes have to be prepared just-in-time and it turn out that 400kHz is too fast for that.
Understood.
Quoted 15 lines
-michael
Quoted 11 lines
Quoted 10 lines
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts new file +10
-0+}; + +/* SER3 */ +&wkup_uart0 { + /* WKUP UART0 is used by Device Manager firmware */ + pinctrl-names = "default"; + pinctrl-0 = <&wkup_uart0_pins_default>; + bootph-all; + status = "reserved"; +};[..]
PATCH v3 3/3 arm64: dts: ti: sa67: add overlay for the ADS2 carrier
In reply to Michael WalleThe SMARC module can be used on the Kontron SMARC 2.2 Evaluation carrier (ads2). Add an overlay to enable all the devices found on the carrier and enable the corresponding peripherals of the SoC.
--- arch/arm64/boot/dts/ti/Makefile | 3 + .../dts/ti/k3-am67a-kontron-sa67-ads2.dtso | 146 ++++++++++++++++++ 2 files changed, 149 insertions(+) create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-ads2.dtso
arch/arm64/boot/dts/ti/Makefile +3 -0
@@ -139,12 +139,15 @@ dtb-$(CONFIG_ARCH_K3) += k3-j721s2-evm-usb0-type-a.dtbo # Boards with J722s SoC k3-am67a-kontron-sa67-dtbs := k3-am67a-kontron-sa67-base.dtb \ k3-am67a-kontron-sa67-rtc-rv8263.dtbo k3-am67a-kontron-sa67-gbe1.dtbo +k3-am67a-kontron-sa67-ads2-dtbs := k3-am67a-kontron-sa67.dtb k3-am67a-kontron-sa67-ads2.dtbo dtb-$(CONFIG_ARCH_K3) += k3-am67a-beagley-ai.dtb dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67.dtb dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-base.dtb dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-gbe1.dtbo dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-gpios.dtbo dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-rtc-rv8263.dtbo +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-ads2.dtb +dtb-$(CONFIG_ARCH_K3) += k3-am67a-kontron-sa67-ads2.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm.dtb dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm-csi2-quad-tevi-ov5640.dtbo
arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-ads2.dtso new file +146 -0
146 lines not on this page · raw message
Signature · 1 line
2.47.3
Hi Michael Walle,
Quoted 16 lines · Michael Walle
This series contains the remaining (device tree) patches for the Kontron SMARC-sAM67 module.
v3:
- dropped all patches which were already applied
- add 'bootph-all' to the usb ctrl node to support DFU boot
- as all MFD bits are now merged, combine the patch which added the system controller node into the main one again
- drop duplicate RTC node. This one was a left over before the rtc node moved into it's own overlay
- add a new overlay for the Kontron SMARC 2.2 evaluation carrier
- add a new SMARC gpio overlay to configure the pinmux correct. This is not integrated into the default device tree because it will conflict with any device tree which will use the pins for different purposes (they are multi function pins)
Quoted 1 line
[...]
I have applied the following to branch ti-next on [1]. Thank you!
[1/3] dt-bindings: arm: ti: Add Kontron SMARC-sAM67 module
commit: 22e1d0d8cda783bee95de578cbda3ad0da8a3eb4
[2/3] arm64: dts: ti: Add support for Kontron SMARC-sAM67
commit: 1c3c4df06f9dee41bff60b93d9f0e67500f798f7
[3/3] arm64: dts: ti: sa67: add overlay for the ADS2 carrier
commit: 0114330e7f92ae4f643fca62e6004631018f48d0All 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
--
Vignesh