From: "wsa@kernel.org" <wsa@kernel.org>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"Chris.Packham@alliedtelesis.co.nz"
<Chris.Packham@alliedtelesis.co.nz>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] P2040/P2041 i2c recovery erratum
Date: Wed, 12 May 2021 17:01:18 +0200 [thread overview]
Message-ID: <20210512150118.GA1004@ninjato> (raw)
In-Reply-To: <4e96247275d559bab133d6c318276fa6be4d7be0.camel@infinera.com>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
> > 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-05-12 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 21:20 [PATCH v3 0/4] P2040/P2041 i2c recovery erratum Chris Packham
2021-05-11 21:20 ` [PATCH v3 1/4] dt-bindings: i2c: mpc: Add fsl,i2c-erratum-a004447 flag Chris Packham
2021-05-11 21:20 ` [PATCH v3 2/4] powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P2041 i2c controllers Chris Packham
2021-05-26 1:02 ` Michael Ellerman
2021-05-11 21:20 ` [PATCH v3 3/4] powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P1010 " Chris Packham
2021-05-26 1:02 ` Michael Ellerman
2021-05-11 21:20 ` [PATCH v3 4/4] i2c: mpc: implement erratum A-004447 workaround Chris Packham
2021-05-11 22:10 ` [PATCH v3 0/4] P2040/P2041 i2c recovery erratum Joakim Tjernlund
2021-05-12 1:48 ` Chris Packham
2021-05-12 8:57 ` Joakim Tjernlund
2021-05-12 15:01 ` wsa [this message]
2021-05-20 3:36 ` Chris Packham
2021-05-25 18:49 ` wsa
2021-05-25 18:53 ` Wolfram Sang
2021-05-26 1:02 ` Michael Ellerman
2021-05-27 19:53 ` Wolfram Sang
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=20210512150118.GA1004@ninjato \
--to=wsa@kernel.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Joakim.Tjernlund@infinera.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=robh+dt@kernel.org \
/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).