From: Frank Li <Frank.li@nxp.com>
To: Stefan Eichenberger <eichest@gmail.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: Wed, 18 Feb 2026 11:26:52 -0500 [thread overview]
Message-ID: <aZXoTGK_v3L4pc-E@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260218150940.131354-3-eichest@gmail.com>
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?
Frank
> only read from I2DR after the bus is not busy anymore. Because this
> requires polling, the read of the last byte is moved outside of the
> interrupt handler.
>
> An example for such a failing transfer is this:
> i2ctransfer -y -a 0 w1@0x00 0x02 r1
> Error: Sending messages failed: Connection timed out
> It does not happen with every device because not all devices react to
> the additional clock cycle.
>
> Fixes: 5f5c2d4579ca ("i2c: imx: prevent rescheduling in non dma mode")
> Cc: <stable@vger.kernel.org> # v6.13+
> Signed-off-by: Stefan Eichenberger <stefan.eichenberger@toradex.com>
> ---
> drivers/i2c/busses/i2c-imx.c | 51 ++++++++++++++++++++++--------------
> 1 file changed, 32 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
> index 56e2a14495a9a..452d120a210b1 100644
> --- a/drivers/i2c/busses/i2c-imx.c
> +++ b/drivers/i2c/busses/i2c-imx.c
> @@ -1018,8 +1018,9 @@ static inline int i2c_imx_isr_read(struct imx_i2c_struct *i2c_imx)
> return 0;
> }
>
> -static inline void i2c_imx_isr_read_continue(struct imx_i2c_struct *i2c_imx)
> +static inline enum imx_i2c_state i2c_imx_isr_read_continue(struct imx_i2c_struct *i2c_imx)
> {
> + enum imx_i2c_state next_state = IMX_I2C_STATE_READ_CONTINUE;
> unsigned int temp;
>
> if ((i2c_imx->msg->len - 1) == i2c_imx->msg_buf_idx) {
> @@ -1033,18 +1034,20 @@ static inline void i2c_imx_isr_read_continue(struct imx_i2c_struct *i2c_imx)
> i2c_imx->stopped = 1;
> temp &= ~(I2CR_MSTA | I2CR_MTX);
> imx_i2c_write_reg(temp, i2c_imx, IMX_I2C_I2CR);
> - } else {
> - /*
> - * For i2c master receiver repeat restart operation like:
> - * read -> repeat MSTA -> read/write
> - * The controller must set MTX before read the last byte in
> - * the first read operation, otherwise the first read cost
> - * one extra clock cycle.
> - */
> - temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
> - temp |= I2CR_MTX;
> - imx_i2c_write_reg(temp, i2c_imx, IMX_I2C_I2CR);
> +
> + return IMX_I2C_STATE_DONE;
> }
> + /*
> + * For i2c master receiver repeat restart operation like:
> + * read -> repeat MSTA -> read/write
> + * The controller must set MTX before read the last byte in
> + * the first read operation, otherwise the first read cost
> + * one extra clock cycle.
> + */
> + temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
> + temp |= I2CR_MTX;
> + imx_i2c_write_reg(temp, i2c_imx, IMX_I2C_I2CR);
> + next_state = IMX_I2C_STATE_DONE;
> } else if (i2c_imx->msg_buf_idx == (i2c_imx->msg->len - 2)) {
> temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
> temp |= I2CR_TXAK;
> @@ -1052,6 +1055,7 @@ static inline void i2c_imx_isr_read_continue(struct imx_i2c_struct *i2c_imx)
> }
>
> i2c_imx->msg->buf[i2c_imx->msg_buf_idx++] = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2DR);
> + return next_state;
> }
>
> static inline void i2c_imx_isr_read_block_data_len(struct imx_i2c_struct *i2c_imx)
> @@ -1088,11 +1092,9 @@ static irqreturn_t i2c_imx_master_isr(struct imx_i2c_struct *i2c_imx, unsigned i
> break;
>
> case IMX_I2C_STATE_READ_CONTINUE:
> - i2c_imx_isr_read_continue(i2c_imx);
> - if (i2c_imx->msg_buf_idx == i2c_imx->msg->len) {
> - i2c_imx->state = IMX_I2C_STATE_DONE;
> + i2c_imx->state = i2c_imx_isr_read_continue(i2c_imx);
> + if (i2c_imx->state == IMX_I2C_STATE_DONE)
> wake_up(&i2c_imx->queue);
> - }
> break;
>
> case IMX_I2C_STATE_READ_BLOCK_DATA:
> @@ -1490,6 +1492,7 @@ static int i2c_imx_read(struct imx_i2c_struct *i2c_imx, struct i2c_msg *msgs,
> bool is_lastmsg)
> {
> int block_data = msgs->flags & I2C_M_RECV_LEN;
> + int ret = 0;
>
> dev_dbg(&i2c_imx->adapter.dev,
> "<%s> write slave address: addr=0x%x\n",
> @@ -1522,10 +1525,20 @@ static int i2c_imx_read(struct imx_i2c_struct *i2c_imx, struct i2c_msg *msgs,
> dev_err(&i2c_imx->adapter.dev, "<%s> read timedout\n", __func__);
> return -ETIMEDOUT;
> }
> - if (i2c_imx->is_lastmsg && !i2c_imx->stopped)
> - return i2c_imx_bus_busy(i2c_imx, 0, false);
> + if (i2c_imx->is_lastmsg) {
> + if (!i2c_imx->stopped)
> + ret = i2c_imx_bus_busy(i2c_imx, 0, false);
> + /*
> + * Only read the last byte of the last message after the bus is
> + * not busy. Else the controller generates another clock which
> + * might confuse devices.
> + */
> + if (!ret)
> + i2c_imx->msg->buf[i2c_imx->msg_buf_idx++] = imx_i2c_read_reg(i2c_imx,
> + IMX_I2C_I2DR);
> + }
>
> - return 0;
> + return ret;
> }
>
> static int i2c_imx_xfer_common(struct i2c_adapter *adapter,
> --
> 2.51.0
>
next prev parent reply other threads:[~2026-02-18 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 15:08 [PATCH v1 0/2] i2c: imx: fix i2c issues when reading messages Stefan Eichenberger
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 [this message]
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=aZXoTGK_v3L4pc-E@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=andi.shyti@kernel.org \
--cc=eichest@gmail.com \
--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