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 02/10] arm64: dts: ti: k3-am62: Enable I2C nodes at the board level
Date: Tue, 18 Oct 2022 16:15:25 -0500 [thread overview]
Message-ID: <20221018211533.21335-3-afd@ti.com> (raw)
In-Reply-To: <20221018211533.21335-1-afd@ti.com>
I2C 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 I2C 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 | 4 ++++
arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 1 +
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 1 +
arch/arm64/boot/dts/ti/k3-am625-sk.dts | 18 ++----------------
4 files changed, 8 insertions(+), 16 deletions(-)
diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
index f6f8ccdb5f55..295c9bb22e7d 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
@@ -271,6 +271,7 @@ main_i2c0: i2c@20000000 {
power-domains = <&k3_pds 102 TI_SCI_PD_EXCLUSIVE>;
clocks = <&k3_clks 102 2>;
clock-names = "fck";
+ status = "disabled";
};
main_i2c1: i2c@20010000 {
@@ -282,6 +283,7 @@ main_i2c1: i2c@20010000 {
power-domains = <&k3_pds 103 TI_SCI_PD_EXCLUSIVE>;
clocks = <&k3_clks 103 2>;
clock-names = "fck";
+ status = "disabled";
};
main_i2c2: i2c@20020000 {
@@ -293,6 +295,7 @@ main_i2c2: i2c@20020000 {
power-domains = <&k3_pds 104 TI_SCI_PD_EXCLUSIVE>;
clocks = <&k3_clks 104 2>;
clock-names = "fck";
+ status = "disabled";
};
main_i2c3: i2c@20030000 {
@@ -304,6 +307,7 @@ main_i2c3: i2c@20030000 {
power-domains = <&k3_pds 105 TI_SCI_PD_EXCLUSIVE>;
clocks = <&k3_clks 105 2>;
clock-names = "fck";
+ status = "disabled";
};
main_spi0: spi@20100000 {
diff --git a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
index 8dff39723628..7f715ebe8e24 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
@@ -33,6 +33,7 @@ mcu_i2c0: i2c@4900000 {
power-domains = <&k3_pds 106 TI_SCI_PD_EXCLUSIVE>;
clocks = <&k3_clks 106 2>;
clock-names = "fck";
+ status = "disabled";
};
mcu_spi0: spi@4b00000 {
diff --git a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
index 94cfc549f644..ff936d547c99 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
@@ -38,5 +38,6 @@ wkup_i2c0: i2c@2b200000 {
power-domains = <&k3_pds 107 TI_SCI_PD_EXCLUSIVE>;
clocks = <&k3_clks 107 4>;
clock-names = "fck";
+ status = "disabled";
};
};
diff --git a/arch/arm64/boot/dts/ti/k3-am625-sk.dts b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
index 0c7b25213e97..c280d6c00412 100644
--- a/arch/arm64/boot/dts/ti/k3-am625-sk.dts
+++ b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
@@ -293,21 +293,15 @@ &main_uart1 {
status = "reserved";
};
-&mcu_i2c0 {
- status = "disabled";
-};
-
-&wkup_i2c0 {
- status = "disabled";
-};
-
&main_i2c0 {
+ status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&main_i2c0_pins_default>;
clock-frequency = <400000>;
};
&main_i2c1 {
+ status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&main_i2c1_pins_default>;
clock-frequency = <400000>;
@@ -340,14 +334,6 @@ exp1: gpio@22 {
};
};
-&main_i2c2 {
- status = "disabled";
-};
-
-&main_i2c3 {
- status = "disabled";
-};
-
&sdhci0 {
pinctrl-names = "default";
pinctrl-0 = <&main_mmc0_pins_default>;
--
2.37.3
next prev 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 ` Andrew Davis [this message]
2022-10-18 21:15 ` [PATCH 03/10] arm64: dts: ti: k3-am62: Enable SPI " Andrew Davis
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-3-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).