From: Stefan Eichenberger <eichest@gmail.com>
To: Frank Li <Frank.li@nxp.com>
Cc: o.rempel@pengutronix.de, kernel@pengutronix.de,
andi.shyti@kernel.org, s.hauer@pengutronix.de,
festevam@gmail.com, stefan.eichenberger@toradex.com,
francesco.dolcini@toradex.com, linux-i2c@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v1 2/2] i2c: imx: ensure no clock is generated after last read
Date: Tue, 3 Mar 2026 10:14:08 +0100 [thread overview]
Message-ID: <aaamYByn9dZEIBWb@eichest-laptop> (raw)
In-Reply-To: <aZXq4gn4xhInQQlq@eichest-laptop>
Hi Frank,
On Wed, Feb 18, 2026 at 05:37:54PM +0100, Stefan Eichenberger wrote:
> Hi Frank,
>
> On Wed, Feb 18, 2026 at 11:26:52AM -0500, Frank Li wrote:
> > On Wed, Feb 18, 2026 at 04:08:50PM +0100, Stefan Eichenberger wrote:
> > > From: Stefan Eichenberger <stefan.eichenberger@toradex.com>
> > >
> > > When reading from the I2DR register, right after releasing the bus by
> > > clearing MSTA and MTX, the I2C controller might still generate an
> > > additional clock cycle which can cause devices to misbehave. Ensure to
> >
> > Do you means SCL have additional toggle? You capture waveform?
> >
>
> Yes exactly. We were able to capture the waveform when the issue
> happens. It doesn't always happen though, it depends on how much time
> passes between clearing MSTA and MTX and reading from I2DR.
>
> If you want to see the waveform, I uploaded it to our server:
> https://share.toradex.com/dwnhcrl6b9toib6
> You can see the additional clock at the right end, after "0x17 + NAK".
Have you had a chance to look at the waveform? Do you have any concerns
about the proposed solution?
Best regards,
Stefan
next prev parent reply other threads:[~2026-03-03 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260218150940.131354-1-eichest@gmail.com>
2026-02-18 15:08 ` [PATCH v1 1/2] i2c: imx: fix i2c issue when reading multiple messages Stefan Eichenberger
2026-02-18 16:22 ` Frank Li
2026-02-18 15:08 ` [PATCH v1 2/2] i2c: imx: ensure no clock is generated after last read Stefan Eichenberger
2026-02-18 16:26 ` Frank Li
2026-02-18 16:37 ` Stefan Eichenberger
2026-03-03 9:14 ` Stefan Eichenberger [this message]
2026-03-03 15:53 ` Frank Li
2026-03-04 3:00 ` Carlos Song
2026-03-19 23:09 ` Andi Shyti
2026-03-20 2:04 ` [EXT] " Carlos Song
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=aaamYByn9dZEIBWb@eichest-laptop \
--to=eichest@gmail.com \
--cc=Frank.li@nxp.com \
--cc=andi.shyti@kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=stable@vger.kernel.org \
--cc=stefan.eichenberger@toradex.com \
/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