From: michael.opdenacker@rootcommit.com
To: linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Cc: Michael Opdenacker <michael.opdenacker@rootcommit.com>
Subject: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
Date: Sat, 25 Oct 2025 07:45:17 +0000 (UTC) [thread overview]
Message-ID: <20251025074514.642357-1-michael.opdenacker@rootcommit.com> (raw)
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
The OrangePi RV2 board exposes i2c2 and i2c8 buses from the Spacemit K1 SoC.
Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
---
arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts b/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts
index 41dc8e35e6eb..c4b25dd30f54 100644
--- a/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts
+++ b/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts
@@ -17,6 +17,8 @@ aliases {
serial0 = &uart0;
ethernet0 = ð0;
ethernet1 = ð1;
+ i2c2 = &i2c2;
+ i2c8 = &i2c8;
};
chosen {
@@ -81,6 +83,18 @@ rgmii1: phy@1 {
};
};
+&i2c2 {
+ pinctrl-0 = <&i2c2_0_cfg>;
+ pinctrl-names = "default";
+ status = "okay";
+};
+
+&i2c8 {
+ pinctrl-0 = <&i2c8_cfg>;
+ pinctrl-names = "default";
+ status = "okay";
+};
+
&pdma {
status = "okay";
};
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2025-10-25 7:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 7:45 michael.opdenacker [this message]
2025-10-25 7:48 ` [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2 Michael Opdenacker
2025-10-27 1:18 ` Troy Mitchell
2025-11-03 2:44 ` Troy Mitchell
2025-11-03 20:51 ` Michael Opdenacker
2025-11-04 1:21 ` Troy Mitchell
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=20251025074514.642357-1-michael.opdenacker@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=linux-riscv@lists.infradead.org \
--cc=spacemit@lists.linux.dev \
/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).