From: Stefan Eichenberger <eichest@gmail.com>
To: o.rempel@pengutronix.de, kernel@pengutronix.de,
andi.shyti@kernel.org, Frank.Li@nxp.com, s.hauer@pengutronix.de,
festevam@gmail.com, stefan.eichenberger@toradex.com,
francesco.dolcini@toradex.com
Cc: linux-i2c@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] i2c: imx: fix i2c issues when reading messages
Date: Wed, 18 Feb 2026 16:08:48 +0100 [thread overview]
Message-ID: <20260218150940.131354-1-eichest@gmail.com> (raw)
This patch series fixes two issues with the imx i2c driver when reading
messages.
The first issue is that after a repeated start the bus is still busy. If
the driver polls for that bus busy bit, the driver will timeout and fail
to read.
The second issue is that after the last message the driver should not
immediately read the data from the data register or an additional clock
will be generated. This can cause devices that react to that clock to
misbehave which will also lead to a timeout.
Stefan Eichenberger (2):
i2c: imx: fix i2c issue when reading multiple messages
i2c: imx: ensure no clock is generated after last read
drivers/i2c/busses/i2c-imx.c | 51 ++++++++++++++++++++++--------------
1 file changed, 32 insertions(+), 19 deletions(-)
--
2.51.0
next reply other threads:[~2026-02-18 15:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 15:08 Stefan Eichenberger [this message]
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
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
2026-03-25 17:32 ` [PATCH v1 0/2] i2c: imx: fix i2c issues when reading messages Andi Shyti
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=20260218150940.131354-1-eichest@gmail.com \
--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=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