public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Yann Sionneau <ysionneau@kalrayinc.com>
To: Tam Nguyen <tamnguyenchi@os.amperecomputing.com>,
	linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Cc: patches@amperecomputing.com, jarkko.nikula@linux.intel.com,
	andriy.shevchenko@linux.intel.com,
	mika.westerberg@linux.intel.com, jsd@semihalf.com,
	chuong@os.amperecomputing.com, darren@os.amperecomputing.com,
	stable@vger.kernel.org
Subject: Re: [PATCH v1] i2c: designware: Disable TX_EMPTY irq while waiting for block length byte
Date: Tue, 3 Oct 2023 10:11:36 +0200	[thread overview]
Message-ID: <9e737b85-95bb-66cd-301c-3a2d1d41f4c8@kalrayinc.com> (raw)
In-Reply-To: <20230929035356.6435-1-tamnguyenchi@os.amperecomputing.com>

Hi Tam,

On 9/29/23 05:53, Tam Nguyen wrote:
> During SMBus block data read process, we have seen high interrupt rate
> because of TX_EMPTY irq status while waiting for block length byte (the
> first data byte after the address phase). The interrupt handler does not
> do anything because the internal state is kept as STATUS_WRITE_IN_PROGRESS.
> Hence, we should disable TX_EMPTY irq until I2C DW receives first data
> byte from I2C device, then re-enable it.
>
> It takes 0.789 ms for host to receive data length from slave.
> Without the patch, i2c_dw_isr is called 99 times by TX_EMPTY interrupt.
> And it is none after applying the patch.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Chuong Tran <chuong@os.amperecomputing.com>
> Signed-off-by: Tam Nguyen <tamnguyenchi@os.amperecomputing.com>
> ---
>   drivers/i2c/busses/i2c-designware-master.c | 13 +++++++++++++
>   1 file changed, 13 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-designware-master.c b/drivers/i2c/busses/i2c-designware-master.c
> index 55ea91a63382..2152b1f9b27c 100644
> --- a/drivers/i2c/busses/i2c-designware-master.c
> +++ b/drivers/i2c/busses/i2c-designware-master.c
> @@ -462,6 +462,13 @@ i2c_dw_xfer_msg(struct dw_i2c_dev *dev)
>   		if (buf_len > 0 || flags & I2C_M_RECV_LEN) {
>   			/* more bytes to be written */
>   			dev->status |= STATUS_WRITE_IN_PROGRESS;
> +			/*
> +			 * In I2C_FUNC_SMBUS_BLOCK_DATA case, there is no data
> +			 * to send before receiving data length from slave.
> +			 * Disable TX_EMPTY while waiting for data length byte
> +			 */
> +			if (flags & I2C_M_RECV_LEN)
> +				intr_mask &= ~DW_IC_INTR_TX_EMPTY;
>   			break;
>   		} else
>   			dev->status &= ~STATUS_WRITE_IN_PROGRESS;
> @@ -485,6 +492,7 @@ i2c_dw_recv_len(struct dw_i2c_dev *dev, u8 len)
>   {
>   	struct i2c_msg *msgs = dev->msgs;
>   	u32 flags = msgs[dev->msg_read_idx].flags;
> +	u32 intr_mask;
>   
>   	/*
>   	 * Adjust the buffer length and mask the flag
> @@ -495,6 +503,11 @@ i2c_dw_recv_len(struct dw_i2c_dev *dev, u8 len)
>   	msgs[dev->msg_read_idx].len = len;
>   	msgs[dev->msg_read_idx].flags &= ~I2C_M_RECV_LEN;
>   
> +	/* Re-enable TX_EMPTY interrupt. */
> +	regmap_read(dev->map, DW_IC_INTR_MASK, &intr_mask);
> +	intr_mask |= DW_IC_INTR_TX_EMPTY;
> +	regmap_write(dev->map, DW_IC_INTR_MASK, intr_mask);
> +
>   	return len;
>   }

I tested this patch on Kalray k200 and k200lp boards (Coolidge SoC, kvx 
arch). With this patch all our CI pipelines are green.

Tested-by: Yann Sionneau <ysionneau@kalrayinc.com>

-- 

Yann






  parent reply	other threads:[~2023-10-03  8:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29  3:53 [PATCH v1] i2c: designware: Disable TX_EMPTY irq while waiting for block length byte Tam Nguyen
2023-09-29 13:43 ` Jarkko Nikula
2023-09-29 16:08 ` Serge Semin
2023-10-16  2:47   ` Tam Chi Nguyen
2023-10-03  8:11 ` Yann Sionneau [this message]
2023-10-16  2:52   ` Tam Chi Nguyen
2023-10-03  8:57 ` Andy Shevchenko
2023-10-16  2:51   ` Tam Chi Nguyen

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=9e737b85-95bb-66cd-301c-3a2d1d41f4c8@kalrayinc.com \
    --to=ysionneau@kalrayinc.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=chuong@os.amperecomputing.com \
    --cc=darren@os.amperecomputing.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jsd@semihalf.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=patches@amperecomputing.com \
    --cc=stable@vger.kernel.org \
    --cc=tamnguyenchi@os.amperecomputing.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