From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Jonas Karlman <jonas@kwiboo.se>, Heiko Stuebner <heiko@sntech.de>
Cc: michael.opdenacker@rootcommit.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: rockchip: Enable i2c2 on Orange Pi 3B
Date: Wed, 26 Nov 2025 08:49:16 +0000 (UTC) [thread overview]
Message-ID: <45aac7ef-a5dc-4e93-bb11-30bb88259974@rootcommit.com> (raw)
In-Reply-To: <d66f81e4-9d9f-4df8-916b-e6f68c85d813@kwiboo.se>
Hi Jonas
Thanks for the review!
On 11/26/25 09:40, Jonas Karlman wrote:
> Hi Michael,
>
> On 11/20/2025 8:00 PM, Michael Opdenacker wrote:
>> Enable the "i2c2" bus on header pins 3 (I2C_SDA_M1)
>> and 5 (I2C2_SCL_M1) of the Orange Pi 3B board.
>>
>> As documented on http://www.orangepi.org/img/pi3b/0719-pi3b-19.png
>> such pins are the only ones offering I2C functionality
>> without conflicting with other SoC blocks.
> This is strictly not true, these pins are by default used as GPIO, this
> patch change them to use the I2C2 func, something that should normally
> be enabled in an overlay.
>
> Functions for these pins:
>
> func 0 func 1
>
> GPIO4_B4_d I2C2_SDA_M1
> GPIO4_B5_d I2C2_SCL_M1
Correct. My idea was that GPIOs are easy to get on other pins, and I
found that I2C2 on such pins would be a convenient default.
>
>> Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
>> ---
>> arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dtsi | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dtsi b/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dtsi
>> index d539570f531e..e2f0ccc6dbe7 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dtsi
>> +++ b/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dtsi
>> @@ -435,6 +435,11 @@ regulator-state-mem {
>> };
>> };
>>
>> +&i2c2 {
>> + pinctrl-0 = <&i2c2m1_xfer>;
> pinctrl-names should also be added here.
Actually, the "pinctrl-names" property is already available in the
definition of i2c2. That's why I didn't add it again.
>
>> + status = "okay";
> As mentioned above, this should be enabled in an DT overlay not in the
> board DT.
I don't mind if my patch is removed, no hard feelings :)
BTW, is there a convenient location for sharing overlays like these?
Some overlays are sometimes tricky to develop, and sharing them with
others is useful for the community. I guess the question was asked
before, but I don't know its answer :)
Thanks again
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
WARNING: multiple messages have this Message-ID (diff)
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Jonas Karlman <jonas@kwiboo.se>, Heiko Stuebner <heiko@sntech.de>
Cc: michael.opdenacker@rootcommit.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: rockchip: Enable i2c2 on Orange Pi 3B
Date: Wed, 26 Nov 2025 08:49:16 +0000 (UTC) [thread overview]
Message-ID: <45aac7ef-a5dc-4e93-bb11-30bb88259974@rootcommit.com> (raw)
In-Reply-To: <d66f81e4-9d9f-4df8-916b-e6f68c85d813@kwiboo.se>
Hi Jonas
Thanks for the review!
On 11/26/25 09:40, Jonas Karlman wrote:
> Hi Michael,
>
> On 11/20/2025 8:00 PM, Michael Opdenacker wrote:
>> Enable the "i2c2" bus on header pins 3 (I2C_SDA_M1)
>> and 5 (I2C2_SCL_M1) of the Orange Pi 3B board.
>>
>> As documented on http://www.orangepi.org/img/pi3b/0719-pi3b-19.png
>> such pins are the only ones offering I2C functionality
>> without conflicting with other SoC blocks.
> This is strictly not true, these pins are by default used as GPIO, this
> patch change them to use the I2C2 func, something that should normally
> be enabled in an overlay.
>
> Functions for these pins:
>
> func 0 func 1
>
> GPIO4_B4_d I2C2_SDA_M1
> GPIO4_B5_d I2C2_SCL_M1
Correct. My idea was that GPIOs are easy to get on other pins, and I
found that I2C2 on such pins would be a convenient default.
>
>> Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
>> ---
>> arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dtsi | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dtsi b/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dtsi
>> index d539570f531e..e2f0ccc6dbe7 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dtsi
>> +++ b/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dtsi
>> @@ -435,6 +435,11 @@ regulator-state-mem {
>> };
>> };
>>
>> +&i2c2 {
>> + pinctrl-0 = <&i2c2m1_xfer>;
> pinctrl-names should also be added here.
Actually, the "pinctrl-names" property is already available in the
definition of i2c2. That's why I didn't add it again.
>
>> + status = "okay";
> As mentioned above, this should be enabled in an DT overlay not in the
> board DT.
I don't mind if my patch is removed, no hard feelings :)
BTW, is there a convenient location for sharing overlays like these?
Some overlays are sometimes tricky to develop, and sharing them with
others is useful for the community. I guess the question was asked
before, but I don't know its answer :)
Thanks again
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-11-26 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 19:00 [PATCH] arm64: dts: rockchip: Enable i2c2 on Orange Pi 3B Michael Opdenacker
2025-11-20 19:00 ` Michael Opdenacker
2025-11-21 21:45 ` Heiko Stuebner
2025-11-21 21:45 ` Heiko Stuebner
2025-11-26 8:40 ` Jonas Karlman
2025-11-26 8:40 ` Jonas Karlman
2025-11-26 8:49 ` Michael Opdenacker [this message]
2025-11-26 8:49 ` Michael Opdenacker
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=45aac7ef-a5dc-4e93-bb11-30bb88259974@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.