linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Troy Mitchell <troy.mitchell@linux.spacemit.com>
To: Michael Opdenacker <michael.opdenacker@rootcommit.com>,
	Troy Mitchell <troy.mitchell@linux.spacemit.com>,
	linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2
Date: Tue, 4 Nov 2025 09:21:59 +0800	[thread overview]
Message-ID: <DA278404237CBF3D+aQlVN4Hnu9b_Mv5l@kernel.org> (raw)
In-Reply-To: <40d90aa9-4ab2-4d8c-939d-337e63179515@rootcommit.com>

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

      reply	other threads:[~2025-11-04  1:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-25  7:45 [RFC PATCH] riscv: dts: spacemit: initial i2c support for OrangePi RV2 michael.opdenacker
2025-10-25  7:48 ` 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 [this message]

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=DA278404237CBF3D+aQlVN4Hnu9b_Mv5l@kernel.org \
    --to=troy.mitchell@linux.spacemit.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michael.opdenacker@rootcommit.com \
    --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).