* Re: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
@ 2025-10-27 1:18 ` Troy Mitchell
0 siblings, 0 replies; 14+ messages in thread
From: Troy Mitchell @ 2025-10-27 1:18 UTC (permalink / raw)
To: Michael Opdenacker, linux-riscv, spacemit; +Cc: Troy Mitchell
On Sat, Oct 25, 2025 at 07:48:45AM +0000, Michael Opdenacker wrote:
> Greetings,
>
> On 10/25/25 09:45, michael.opdenacker@rootcommit.com wrote:
> > From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
[...]
> > +&i2c2 {
> > + pinctrl-0 = <&i2c2_0_cfg>;
> > + pinctrl-names = "default";
> > + status = "okay";
> > +};
> > +
> > +&i2c8 {
> > + pinctrl-0 = <&i2c8_cfg>;
> > + pinctrl-names = "default";
> > + status = "okay";
> > +};
> > +
> > &pdma {
> > status = "okay";
> > };
>
>
> Unfortunately, these changes are not functional yet on OrangePi RV2, testing
> on https://github.com/spacemit-com/linux/commits/k1/dt-for-next
>
> # i2cdetect -r 2
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c-2 using receive byte commands.
> I will probe address range 0x08-0x77.
> Continue? [Y/n]
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: [ 124.675321] i2c-k1 d4012000.i2c: i2c transfer failed, ret -11
> err 0x400000
[...]
> -- 09 [ 124.686769] i2c-k1 d4012000.i2c: i2c transfer
> I assume the i2c-k1 driver works on BananaPi F3.
No, It doesn't work on BananaPi F3 actually.
> Any clues why the same
> buses don't work OrangePi RV2?
This is a known issue.
I didn’t fix it earlier since it doesn’t affect functionality,
but now that it’s been reported, it’s time to fix it.
I’ll send a patch shortly.
Thanks for reporting this issue.
- Troy
> Thanks in advance
> Cheers
> Michael.
>
> --
> Michael Opdenacker
> Root Commit
> Yocto Project and OpenEmbedded Training course - Learn by doing:
> https://rootcommit.com/training/yocto/
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
2025-10-27 1:18 ` Troy Mitchell
@ 2025-11-03 2:44 ` Troy Mitchell
-1 siblings, 0 replies; 14+ messages in thread
From: Troy Mitchell @ 2025-11-03 2:44 UTC (permalink / raw)
To: Michael Opdenacker, linux-riscv, spacemit; +Cc: Troy Mitchell
On Mon, Oct 27, 2025 at 09:18:50AM +0800, Troy Mitchell wrote:
> On Sat, Oct 25, 2025 at 07:48:45AM +0000, Michael Opdenacker wrote:
> > Greetings,
> >
> > On 10/25/25 09:45, michael.opdenacker@rootcommit.com wrote:
> > > From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
> [...]
> > > +&i2c2 {
> > > + pinctrl-0 = <&i2c2_0_cfg>;
> > > + pinctrl-names = "default";
> > > + status = "okay";
> > > +};
> > > +
> > > +&i2c8 {
> > > + pinctrl-0 = <&i2c8_cfg>;
> > > + pinctrl-names = "default";
> > > + status = "okay";
> > > +};
> > > +
> > > &pdma {
> > > status = "okay";
> > > };
> >
> >
> > Unfortunately, these changes are not functional yet on OrangePi RV2, testing
> > on https://github.com/spacemit-com/linux/commits/k1/dt-for-next
> >
> > # i2cdetect -r 2
> > WARNING! This program can confuse your I2C bus, cause data loss and worse!
> > I will probe file /dev/i2c-2 using receive byte commands.
> > I will probe address range 0x08-0x77.
> > Continue? [Y/n]
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > 00: [ 124.675321] i2c-k1 d4012000.i2c: i2c transfer failed, ret -11
> > err 0x400000
I recall that the PMIC sometimes reports I2C timeouts.
Could you please confirm if you’re seeing this issue on your side?
If so, does it still occur when using my branch?
Thanks!
- Troy
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
@ 2025-11-03 2:44 ` Troy Mitchell
0 siblings, 0 replies; 14+ messages in thread
From: Troy Mitchell @ 2025-11-03 2:44 UTC (permalink / raw)
To: Michael Opdenacker, linux-riscv, spacemit; +Cc: Troy Mitchell
On Mon, Oct 27, 2025 at 09:18:50AM +0800, Troy Mitchell wrote:
> On Sat, Oct 25, 2025 at 07:48:45AM +0000, Michael Opdenacker wrote:
> > Greetings,
> >
> > On 10/25/25 09:45, michael.opdenacker@rootcommit.com wrote:
> > > From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
> [...]
> > > +&i2c2 {
> > > + pinctrl-0 = <&i2c2_0_cfg>;
> > > + pinctrl-names = "default";
> > > + status = "okay";
> > > +};
> > > +
> > > +&i2c8 {
> > > + pinctrl-0 = <&i2c8_cfg>;
> > > + pinctrl-names = "default";
> > > + status = "okay";
> > > +};
> > > +
> > > &pdma {
> > > status = "okay";
> > > };
> >
> >
> > Unfortunately, these changes are not functional yet on OrangePi RV2, testing
> > on https://github.com/spacemit-com/linux/commits/k1/dt-for-next
> >
> > # i2cdetect -r 2
> > WARNING! This program can confuse your I2C bus, cause data loss and worse!
> > I will probe file /dev/i2c-2 using receive byte commands.
> > I will probe address range 0x08-0x77.
> > Continue? [Y/n]
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > 00: [ 124.675321] i2c-k1 d4012000.i2c: i2c transfer failed, ret -11
> > err 0x400000
I recall that the PMIC sometimes reports I2C timeouts.
Could you please confirm if you’re seeing this issue on your side?
If so, does it still occur when using my branch?
Thanks!
- Troy
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
2025-11-03 2:44 ` Troy Mitchell
@ 2025-11-03 20:51 ` Michael Opdenacker
-1 siblings, 0 replies; 14+ messages in thread
From: Michael Opdenacker @ 2025-11-03 20:51 UTC (permalink / raw)
To: Troy Mitchell, linux-riscv, spacemit; +Cc: michael.opdenacker
Hi Troy,
On 11/3/25 03:44, Troy Mitchell wrote:
>>> Unfortunately, these changes are not functional yet on OrangePi RV2, testing
>>> on https://github.com/spacemit-com/linux/commits/k1/dt-for-next
>>>
>>> # i2cdetect -r 2
>>> WARNING! This program can confuse your I2C bus, cause data loss and worse!
>>> I will probe file /dev/i2c-2 using receive byte commands.
>>> I will probe address range 0x08-0x77.
>>> Continue? [Y/n]
>>> 0 1 2 3 4 5 6 7 8 9 a b c d e f
>>> 00: [ 124.675321] i2c-k1 d4012000.i2c: i2c transfer failed, ret -11
>>> err 0x400000
> I recall that the PMIC sometimes reports I2C timeouts.
> Could you please confirm if you’re seeing this issue on your side?
> If so, does it still occur when using my branch?
Unfortunately, I can't try at the moment, not having the board this
week. I'll be able to test again next week-end. However, I don't
remember having it with your changes.
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
@ 2025-11-03 20:51 ` Michael Opdenacker
0 siblings, 0 replies; 14+ messages in thread
From: Michael Opdenacker @ 2025-11-03 20:51 UTC (permalink / raw)
To: Troy Mitchell, linux-riscv, spacemit; +Cc: michael.opdenacker
Hi Troy,
On 11/3/25 03:44, Troy Mitchell wrote:
>>> Unfortunately, these changes are not functional yet on OrangePi RV2, testing
>>> on https://github.com/spacemit-com/linux/commits/k1/dt-for-next
>>>
>>> # i2cdetect -r 2
>>> WARNING! This program can confuse your I2C bus, cause data loss and worse!
>>> I will probe file /dev/i2c-2 using receive byte commands.
>>> I will probe address range 0x08-0x77.
>>> Continue? [Y/n]
>>> 0 1 2 3 4 5 6 7 8 9 a b c d e f
>>> 00: [ 124.675321] i2c-k1 d4012000.i2c: i2c transfer failed, ret -11
>>> err 0x400000
> I recall that the PMIC sometimes reports I2C timeouts.
> Could you please confirm if you’re seeing this issue on your side?
> If so, does it still occur when using my branch?
Unfortunately, I can't try at the moment, not having the board this
week. I'll be able to test again next week-end. However, I don't
remember having it with your changes.
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
2025-11-03 20:51 ` Michael Opdenacker
@ 2025-11-04 1:21 ` Troy Mitchell
-1 siblings, 0 replies; 14+ messages in thread
From: Troy Mitchell @ 2025-11-04 1:21 UTC (permalink / raw)
To: Michael Opdenacker, Troy Mitchell, linux-riscv, spacemit
On Mon, Nov 03, 2025 at 08:51:11PM +0000, Michael Opdenacker wrote:
> Hi Troy,
>
> On 11/3/25 03:44, Troy Mitchell wrote:
> > > > Unfortunately, these changes are not functional yet on OrangePi RV2, testing
> > > > on https://github.com/spacemit-com/linux/commits/k1/dt-for-next
> > > >
> > > > # i2cdetect -r 2
> > > > WARNING! This program can confuse your I2C bus, cause data loss and worse!
> > > > I will probe file /dev/i2c-2 using receive byte commands.
> > > > I will probe address range 0x08-0x77.
> > > > Continue? [Y/n]
> > > > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > > > 00: [ 124.675321] i2c-k1 d4012000.i2c: i2c transfer failed, ret -11
> > > > err 0x400000
> > I recall that the PMIC sometimes reports I2C timeouts.
> > Could you please confirm if you’re seeing this issue on your side?
> > If so, does it still occur when using my branch?
> Unfortunately, I can't try at the moment, not having the board this week.
> I'll be able to test again next week-end.
Thanks!
>
> However, I don't remember having
> it with your changes.
I forgot to put my link.
Here: https://github.com/Troyself/spacemit/tree/k1/fix-i2c-detect
- Troy
> Cheers
> Michael.
> --
>
> Michael Opdenacker
> Root Commit
> Embedded Linux Training and Consulting
> https://rootcommit.com
>
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
@ 2025-11-04 1:21 ` Troy Mitchell
0 siblings, 0 replies; 14+ messages in thread
From: Troy Mitchell @ 2025-11-04 1:21 UTC (permalink / raw)
To: Michael Opdenacker, Troy Mitchell, linux-riscv, spacemit
On Mon, Nov 03, 2025 at 08:51:11PM +0000, Michael Opdenacker wrote:
> Hi Troy,
>
> On 11/3/25 03:44, Troy Mitchell wrote:
> > > > Unfortunately, these changes are not functional yet on OrangePi RV2, testing
> > > > on https://github.com/spacemit-com/linux/commits/k1/dt-for-next
> > > >
> > > > # i2cdetect -r 2
> > > > WARNING! This program can confuse your I2C bus, cause data loss and worse!
> > > > I will probe file /dev/i2c-2 using receive byte commands.
> > > > I will probe address range 0x08-0x77.
> > > > Continue? [Y/n]
> > > > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > > > 00: [ 124.675321] i2c-k1 d4012000.i2c: i2c transfer failed, ret -11
> > > > err 0x400000
> > I recall that the PMIC sometimes reports I2C timeouts.
> > Could you please confirm if you’re seeing this issue on your side?
> > If so, does it still occur when using my branch?
> Unfortunately, I can't try at the moment, not having the board this week.
> I'll be able to test again next week-end.
Thanks!
>
> However, I don't remember having
> it with your changes.
I forgot to put my link.
Here: https://github.com/Troyself/spacemit/tree/k1/fix-i2c-detect
- Troy
> Cheers
> Michael.
> --
>
> Michael Opdenacker
> Root Commit
> Embedded Linux Training and Consulting
> https://rootcommit.com
>
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
2025-10-27 1:18 ` Troy Mitchell
@ 2025-11-14 13:33 ` Troy Mitchell
-1 siblings, 0 replies; 14+ messages in thread
From: Troy Mitchell @ 2025-11-14 13:33 UTC (permalink / raw)
To: Michael Opdenacker, linux-riscv, spacemit; +Cc: Troy Mitchell
On Mon, Oct 27, 2025 at 09:18:50AM +0800, Troy Mitchell wrote:
> On Sat, Oct 25, 2025 at 07:48:45AM +0000, Michael Opdenacker wrote:
> > Greetings,
> >
> > On 10/25/25 09:45, michael.opdenacker@rootcommit.com wrote:
> > > From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
> [...]
> > > +&i2c2 {
> > > + pinctrl-0 = <&i2c2_0_cfg>;
> > > + pinctrl-names = "default";
> > > + status = "okay";
> > > +};
> > > +
> > > +&i2c8 {
> > > + pinctrl-0 = <&i2c8_cfg>;
> > > + pinctrl-names = "default";
> > > + status = "okay";
> > > +};
> > > +
> > > &pdma {
> > > status = "okay";
> > > };
> >
> >
> > Unfortunately, these changes are not functional yet on OrangePi RV2, testing
> > on https://github.com/spacemit-com/linux/commits/k1/dt-for-next
> >
> > # i2cdetect -r 2
> > WARNING! This program can confuse your I2C bus, cause data loss and worse!
> > I will probe file /dev/i2c-2 using receive byte commands.
> > I will probe address range 0x08-0x77.
> > Continue? [Y/n]
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > 00: [ 124.675321] i2c-k1 d4012000.i2c: i2c transfer failed, ret -11
> > err 0x400000
> [...]
>
> > -- 09 [ 124.686769] i2c-k1 d4012000.i2c: i2c transfer
> > I assume the i2c-k1 driver works on BananaPi F3.
> No, It doesn't work on BananaPi F3 actually.
> > Any clues why the same
> > buses don't work OrangePi RV2?
> This is a known issue.
> I didn’t fix it earlier since it doesn’t affect functionality,
> but now that it’s been reported, it’s time to fix it.
> I’ll send a patch shortly.
>
> Thanks for reporting this issue.
Fixed here: https://lore.kernel.org/all/20251113-fix-k1-detect-failure-v2-1-b02a9a74f65a@linux.spacemit.com/
- Troy
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
@ 2025-11-14 13:33 ` Troy Mitchell
0 siblings, 0 replies; 14+ messages in thread
From: Troy Mitchell @ 2025-11-14 13:33 UTC (permalink / raw)
To: Michael Opdenacker, linux-riscv, spacemit; +Cc: Troy Mitchell
On Mon, Oct 27, 2025 at 09:18:50AM +0800, Troy Mitchell wrote:
> On Sat, Oct 25, 2025 at 07:48:45AM +0000, Michael Opdenacker wrote:
> > Greetings,
> >
> > On 10/25/25 09:45, michael.opdenacker@rootcommit.com wrote:
> > > From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
> [...]
> > > +&i2c2 {
> > > + pinctrl-0 = <&i2c2_0_cfg>;
> > > + pinctrl-names = "default";
> > > + status = "okay";
> > > +};
> > > +
> > > +&i2c8 {
> > > + pinctrl-0 = <&i2c8_cfg>;
> > > + pinctrl-names = "default";
> > > + status = "okay";
> > > +};
> > > +
> > > &pdma {
> > > status = "okay";
> > > };
> >
> >
> > Unfortunately, these changes are not functional yet on OrangePi RV2, testing
> > on https://github.com/spacemit-com/linux/commits/k1/dt-for-next
> >
> > # i2cdetect -r 2
> > WARNING! This program can confuse your I2C bus, cause data loss and worse!
> > I will probe file /dev/i2c-2 using receive byte commands.
> > I will probe address range 0x08-0x77.
> > Continue? [Y/n]
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > 00: [ 124.675321] i2c-k1 d4012000.i2c: i2c transfer failed, ret -11
> > err 0x400000
> [...]
>
> > -- 09 [ 124.686769] i2c-k1 d4012000.i2c: i2c transfer
> > I assume the i2c-k1 driver works on BananaPi F3.
> No, It doesn't work on BananaPi F3 actually.
> > Any clues why the same
> > buses don't work OrangePi RV2?
> This is a known issue.
> I didn’t fix it earlier since it doesn’t affect functionality,
> but now that it’s been reported, it’s time to fix it.
> I’ll send a patch shortly.
>
> Thanks for reporting this issue.
Fixed here: https://lore.kernel.org/all/20251113-fix-k1-detect-failure-v2-1-b02a9a74f65a@linux.spacemit.com/
- Troy
^ permalink raw reply [flat|nested] 14+ messages in thread