[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YK1GuD8o7k+jDLFZ@kunai>
Date: Tue, 25 May 2021 20:49:28 +0200
From: "wsa@...nel.org" <wsa@...nel.org>
To: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
Cc: Joakim Tjernlund <Joakim.Tjernlund@...inera.com>,
"andy.shevchenko@...il.com" <andy.shevchenko@...il.com>,
"andriy.shevchenko@...ux.intel.com"
<andriy.shevchenko@...ux.intel.com>,
"mpe@...erman.id.au" <mpe@...erman.id.au>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/4] P2040/P2041 i2c recovery erratum
> For those reading along the v2 mentioned in that thread was posted as
> https://lore.kernel.org/linux-i2c/20170511122033.22471-1-joakim.tjernlund@infinera.com/
> there was a bit of discussion but it seemed to die out without reaching
> a conclusion.
>
> The i2c-mpc driver is now using the generic recovery mechanism so that
> addresses one bit of feedback from the original thread.
Yes, and the generic recovery has been improved since then. There is an
"incomplete_write_byte" fault injector now and the generic recovery
handles it correctly meanwhile. Before, it actually could cause a write
to happen but we are sending STOPs now.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists