[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+V-a8scyG5Gbo0b+0TKxaYPRn+u1jDHjyzgqb4x7C5x1FUX1w@mail.gmail.com>
Date: Fri, 2 May 2025 10:29:30 +0100
From: "Lad, Prabhakar" <prabhakar.csengg@...il.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
"Lad, Prabhakar" <prabhakar.csengg@...il.com>, Chris Brandt <chris.brandt@...esas.com>,
Andi Shyti <andi.shyti@...nel.org>, Geert Uytterhoeven <geert+renesas@...der.be>,
Andy Shevchenko <andy@...nel.org>, linux-renesas-soc@...r.kernel.org,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
Biju Das <biju.das.jz@...renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@...esas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [PATCH v9 2/2] i2c: riic: Recover from arbitration loss
Hi Wolfram,
On Thu, May 1, 2025 at 8:44 PM Wolfram Sang
<wsa+renesas@...g-engineering.com> wrote:
>
>
> > From 10µs to 50µs, the clock pulses are part of the recovery sequence.
>
> Ahh, that explains. I thought this was all after the recovery.
>
> > Around 55µs, the transfer function starts attempting to send data
> > hence the clock pulse.
>
> The short SCL spike around 55us is still strange. However, we might
> violate t:buf time between STOP and START. Can you please try the
> attached WIP patch?
>
I'm seeing the same behaviour as seen previously (attached is the capture).
> > The slave device is versa clock geberator 5P35023 (exact part number
> > on SMARC RZ/G2L 5P35023B-629NLGI)
>
> Hmm, G3S has a versa clock generator as well. But I can't find a way to
> wire GPIO lines to RIIC1 or I2C_PM.
>
Yes, same here apart from soldering the pins there seems to be no option.
Cheers,
Prabhakar
Download attachment "Screenshot (379).png" of type "image/png" (124051 bytes)
Powered by blists - more mailing lists