From: Miotsuki Mizuno <founder@crepuse.com>
To: "heiko@sntech.de" <heiko@sntech.de>
Cc: "conor+dt@kernel.org" <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"robh@kernel.org" <robh@kernel.org>
Subject: [PATCH] arm64: dts: rockchip: Enable I2C2 on UNIHIKER M10 V1.2
Date: Sat, 10 Oct 2026 23:28:35 +0000 [thread overview]
Message-ID: <20261010232831.26908-1-founder@crepuse.com> (raw)
The onboard resistive touchscreen controller is connected to I2C2.
Enable the controller at the tested 400 kHz bus frequency. Its GPIO2_A2
and GPIO2_A3 pinmux is provided by rk3308.dtsi.
Keep the bus enablement separate from the touchscreen device node so
it can be reviewed without depending on the pending NS2009 binding
and driver. The controller-only configuration was booted on M10 V1.2
with no NS2009 device instantiated.
Signed-off-by: Mizuno Miotsuki <founder@crepuse.com>
---
arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts b/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts
index 270ea970c95a..0c03f118378a 100644
--- a/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts
@@ -131,6 +131,11 @@ &emmc {
status = "okay";
};
+&i2c2 {
+ clock-frequency = <400000>;
+ status = "okay";
+};
+
&io_domains {
vccio0-supply = <&vcc_io>;
vccio1-supply = <&vcc_io>;
base-commit: ae965b9856f033145e292b0c29082a26bcc45efd
--
2.56.0
reply other threads:[~2026-10-10 23:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261010232831.26908-1-founder@crepuse.com \
--to=founder@crepuse.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®