devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Davis <afd@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Bryan Brattlof <bb@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Andrew Davis <afd@ti.com>
Subject: [PATCH 03/10] arm64: dts: ti: k3-am62: Enable SPI nodes at the board level
Date: Tue, 18 Oct 2022 16:15:26 -0500	[thread overview]
Message-ID: <20221018211533.21335-4-afd@ti.com> (raw)
In-Reply-To: <20221018211533.21335-1-afd@ti.com>

SPI nodes defined in the top-level AM62x 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>
---
 arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 3 +++
 arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi  | 2 ++
 2 files changed, 5 insertions(+)

diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
index 295c9bb22e7d..83ac2e45998d 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
@@ -318,6 +318,7 @@ main_spi0: spi@20100000 {
 		#size-cells = <0>;
 		power-domains = <&k3_pds 141 TI_SCI_PD_EXCLUSIVE>;
 		clocks = <&k3_clks 172 0>;
+		status = "disabled";
 	};
 
 	main_spi1: spi@20110000 {
@@ -328,6 +329,7 @@ main_spi1: spi@20110000 {
 		#size-cells = <0>;
 		power-domains = <&k3_pds 142 TI_SCI_PD_EXCLUSIVE>;
 		clocks = <&k3_clks 173 0>;
+		status = "disabled";
 	};
 
 	main_spi2: spi@20120000 {
@@ -338,6 +340,7 @@ main_spi2: spi@20120000 {
 		#size-cells = <0>;
 		power-domains = <&k3_pds 143 TI_SCI_PD_EXCLUSIVE>;
 		clocks = <&k3_clks 174 0>;
+		status = "disabled";
 	};
 
 	main_gpio_intr: interrupt-controller@a00000 {
diff --git a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
index 7f715ebe8e24..28daf476e6a9 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
@@ -44,6 +44,7 @@ mcu_spi0: spi@4b00000 {
 		#size-cells = <0>;
 		power-domains = <&k3_pds 147 TI_SCI_PD_EXCLUSIVE>;
 		clocks = <&k3_clks 147 0>;
+		status = "disabled";
 	};
 
 	mcu_spi1: spi@4b10000 {
@@ -54,6 +55,7 @@ mcu_spi1: spi@4b10000 {
 		#size-cells = <0>;
 		power-domains = <&k3_pds 148 TI_SCI_PD_EXCLUSIVE>;
 		clocks = <&k3_clks 148 0>;
+		status = "disabled";
 	};
 
 	mcu_gpio_intr: interrupt-controller@4210000 {
-- 
2.37.3


  parent reply	other threads:[~2022-10-18 21:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 21:15 [PATCH 00/10] AM62x Disable Incomplete DT Nodes Andrew Davis
2022-10-18 21:15 ` [PATCH 01/10] arm64: dts: ti: k3-am62: Enable UART nodes at the board level Andrew Davis
2022-10-18 21:15 ` [PATCH 02/10] arm64: dts: ti: k3-am62: Enable I2C " Andrew Davis
2022-10-18 21:15 ` Andrew Davis [this message]
2022-10-18 21:15 ` [PATCH 04/10] arm64: dts: ti: k3-am62: Enable EPWM " Andrew Davis
2022-10-18 21:15 ` [PATCH 05/10] arm64: dts: ti: k3-am62: Enable ECAP " Andrew Davis
2022-10-18 21:15 ` [PATCH 06/10] arm64: dts: ti: k3-am62: MDIO pinmux should belong to the MDIO node Andrew Davis
2022-10-18 21:15 ` [PATCH 07/10] arm64: dts: ti: k3-am62: Enable MDIO nodes at the board level Andrew Davis
2022-10-18 21:15 ` [PATCH 08/10] arm64: dts: ti: k3-am62: Enable MCAN " Andrew Davis
2022-10-18 21:15 ` [PATCH 09/10] arm64: dts: ti: k3-am62: Enable SDHCI " Andrew Davis
2022-10-18 21:15 ` [PATCH 10/10] arm64: dts: ti: k3-am62: Enable OSPI " Andrew Davis
2022-10-19 15:19 ` [PATCH 00/10] AM62x Disable Incomplete DT Nodes Bryan Brattlof
2022-10-28 13:15 ` Vignesh Raghavendra
2022-10-28 13:31 ` Nishanth Menon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221018211533.21335-4-afd@ti.com \
    --to=afd@ti.com \
    --cc=bb@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).