From: Udit Kumar <u-kumar1@ti.com>
To: <linux-arm-kernel@lists.infradead.org>, <afd@ti.com>, <bb@ti.com>,
<vaishnav.a@ti.com>, <j-choudhary@ti.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<a-govindraju@ti.com>, <kishon@ti.com>
Cc: Udit Kumar <u-kumar1@ti.com>
Subject: [PATCH 2/2] arm64: dts: ti: k3-j7200-common-proc-board: Enable I2C
Date: Fri, 14 Apr 2023 23:44:34 +0530 [thread overview]
Message-ID: <20230414181434.2046049-3-u-kumar1@ti.com> (raw)
In-Reply-To: <20230414181434.2046049-1-u-kumar1@ti.com>
All I2C nodes were disabled in SOC dts file and in board
dts needed nodes were enabled.
This patch enables wkup_i2c0 node in board dts file.
Fixes: a9ed915cd55c ("arm64: dts: ti: k3-j7200: Enable I2C nodes at the board level")
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
---
arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts b/arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts
index 63633e4f6c59..e66bbfe65ff2 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts
+++ b/arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts
@@ -254,6 +254,10 @@ exp3: gpio@20 {
};
};
+&wkup_i2c0 {
+ status = "okay";
+};
+
&main_sdhci0 {
/* eMMC */
non-removable;
--
2.34.1
next prev parent reply other threads:[~2023-04-14 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 18:14 [PATCH 0/2] arm64: dts: ti: k3-j7200-common-proc-board fixes Udit Kumar
2023-04-14 18:14 ` [PATCH 1/2] arm64: dts: ti: k3-j7200: Fix physical address of pin Udit Kumar
2023-04-14 18:26 ` Nishanth Menon
2023-04-15 4:10 ` Kumar, Udit
2023-04-15 12:47 ` Nishanth Menon
2023-04-14 18:14 ` Udit Kumar [this message]
2023-04-14 18:24 ` [PATCH 2/2] arm64: dts: ti: k3-j7200-common-proc-board: Enable I2C Nishanth Menon
2023-04-15 4:06 ` Kumar, Udit
2023-04-15 12:47 ` 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=20230414181434.2046049-3-u-kumar1@ti.com \
--to=u-kumar1@ti.com \
--cc=a-govindraju@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@ti.com \
--cc=kishon@ti.com \
--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=vaishnav.a@ti.com \
--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