diff options
| author | Andrew Davis <afd@ti.com> | 2022-10-17 14:25:25 -0500 |
|---|---|---|
| committer | Nishanth Menon <nm@ti.com> | 2022-10-28 08:14:48 -0500 |
| commit | 79d4aa623f6c9d47aa29b6b4a3fa46c09f74bfae (patch) | |
| tree | 7f3eddaa7064cac5c8c6f0487b515ee753db1136 /arch/arm64/boot/dts/ti/k3-am642-evm.dts | |
| parent | b80f75d8f68cad4efa250e4a3152932f59c756cc (diff) | |
| download | linux-stable-79d4aa623f6c9d47aa29b6b4a3fa46c09f74bfae.tar.gz linux-stable-79d4aa623f6c9d47aa29b6b4a3fa46c09f74bfae.tar.bz2 linux-stable-79d4aa623f6c9d47aa29b6b4a3fa46c09f74bfae.zip | |
arm64: dts: ti: k3-am64: Enable SPI nodes at the board level
SPI nodes defined in the top-level AM64x SoC dtsi files are incomplete
and will not be functional unless they are extended with pinmux
information.
As the pinmux is only known at the board integration level, these
nodes should only be enabled when provided with this information.
Disable the SPI nodes in the dtsi files and only enable the ones that
are actually pinned out on a given board.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Bryan Brattlof <bb@ti.com>
Acked-by: Vignesh Raghavendra <vigneshr@ti.com>
Link: https://lore.kernel.org/r/20221017192532.23825-4-afd@ti.com
Diffstat (limited to 'arch/arm64/boot/dts/ti/k3-am642-evm.dts')
| -rw-r--r-- | arch/arm64/boot/dts/ti/k3-am642-evm.dts | 9 |
1 files changed, 1 insertions, 8 deletions
diff --git a/arch/arm64/boot/dts/ti/k3-am642-evm.dts b/arch/arm64/boot/dts/ti/k3-am642-evm.dts index 3903e907244e..12d971c3bc3a 100644 --- a/arch/arm64/boot/dts/ti/k3-am642-evm.dts +++ b/arch/arm64/boot/dts/ti/k3-am642-evm.dts @@ -379,15 +379,8 @@ status = "reserved"; }; -&mcu_spi0 { - status = "disabled"; -}; - -&mcu_spi1 { - status = "disabled"; -}; - &main_spi0 { + status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&main_spi0_pins_default>; ti,pindir-d0-out-d1-in; |