Re: [PATCH] i2c: ocores: set IACK bit after core is enabled

From: grygorii tertychnyi
Date: Mon May 20 2024 - 11:02:00 EST


On Mon, May 20, 2024 at 3:41 PM Andrew Lunn <andrew@xxxxxxx> wrote:
>
> On Mon, May 20, 2024 at 03:30:43PM +0200, grygorii tertychnyi wrote:
> > On Sun, May 19, 2024 at 7:25 AM Markus Elfring <Markus.Elfring@xxxxxx> wrote:
> > >
> > > …
> > > > Sometimes it causes failure for the very first message transfer, …
> > >
> > > Does such an information indicate the need for the tag “Fixes”?
> >
> > I'm not sure: the original initialization order was introduced by the
> > very first commit
> > 18f98b1e3147 ("[PATCH] i2c: New bus driver for the OpenCores I2C controller").
>
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>
> It fixes a problem like an oops, a hang, data corruption, a real
> security issue, a hardware quirk, a build error (but not for things
> marked CONFIG_BROKEN), or some “oh, that’s not good” issue.
>
> Your description of the very first message transfer failing sounds
> like a data corruption? Using the commit which adds the driver is also
> fine, some bugs have been there all the time.

Thanks! Yes, it is a data corruption.

> Remember to add a
>
> Cc: stable@xxxxxxxxxxxxxxx

I will send v2.

Regards,
Grygorii