[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210512150118.GA1004@ninjato>
Date: Wed, 12 May 2021 17:01:18 +0200
From: "wsa@...nel.org" <wsa@...nel.org>
To: Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
Cc: "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>,
"Chris.Packham@...iedtelesis.co.nz"
<Chris.Packham@...iedtelesis.co.nz>,
"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
> > I've been doing my recent work with a P2040 and prior to that I did test
> > out the recovery on a T2081 (which isn't documented to have this
> > erratum) when I was re-working the driver. The "new" recovery actually
> > seems better but I don't have a reliably faulty i2c device so that's
> > only based on me writing some code to manually trigger the recovery
> > (using the snippet below) and observing it with an oscilloscope.
>
> You don't need a faulty device, just an aborted I2C read/write op.
If you can wire GPIOs to the bus, you can use the I2C fault injector:
Documentation/i2c/gpio-fault-injection.rst
There are already two "incomplete transfer" injectors.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists