linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Lucas Tanure <tanureal@opensource.cirrus.com>,
	Michal Simek <michal.simek@xilinx.com>,
	Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<patches@opensource.cirrus.com>
Subject: Re: [PATCH] i2c: cadence: Increase timeout per message if necessary
Date: Mon, 21 Mar 2022 16:57:13 +0100	[thread overview]
Message-ID: <dd26fa4a-870e-d969-04df-1f42487e2b54@xilinx.com> (raw)
In-Reply-To: <20220309093147.102385-1-tanureal@opensource.cirrus.com>

+Shubhrajyoti

On 3/9/22 10:31, Lucas Tanure wrote:
> Timeout as 1 second sets a upper limit on the length of
> the transfer executed, but there is no maximum length of
> a write or read message set in i2c_adapter_quirks for this
> controller.

nit: I would expect that you have run any test and you reached an issue.
Would be good to describe what exactly you have tried on which configuration to 
make it super clear.

> 
> To remove that limitation calculate the minimal time
> necessary, plus some wiggle room, for every message
> and use it instead of the default one second, if
> more than one second.
> 
> Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
> ---
>   drivers/i2c/busses/i2c-cadence.c | 12 ++++++++++--
>   1 file changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/i2c/busses/i2c-cadence.c b/drivers/i2c/busses/i2c-cadence.c
> index 805c77143a0f..b4c1ad19cdae 100644
> --- a/drivers/i2c/busses/i2c-cadence.c
> +++ b/drivers/i2c/busses/i2c-cadence.c
> @@ -760,7 +760,7 @@ static void cdns_i2c_master_reset(struct i2c_adapter *adap)
>   static int cdns_i2c_process_msg(struct cdns_i2c *id, struct i2c_msg *msg,
>   		struct i2c_adapter *adap)
>   {
> -	unsigned long time_left;
> +	unsigned long time_left, msg_timeout;
>   	u32 reg;
>   
>   	id->p_msg = msg;
> @@ -785,8 +785,16 @@ static int cdns_i2c_process_msg(struct cdns_i2c *id, struct i2c_msg *msg,
>   	else
>   		cdns_i2c_msend(id);
>   
> +	/* Minimal time to execute this message */
> +	msg_timeout = msecs_to_jiffies((1000 * msg->len * BITS_PER_BYTE) / id->i2c_clk);
> +	/* Plus some wiggle room */
> +	msg_timeout += msecs_to_jiffies(500);
> +
> +	if (msg_timeout < adap->timeout)
> +		msg_timeout = adap->timeout;
> +
>   	/* Wait for the signal of completion */
> -	time_left = wait_for_completion_timeout(&id->xfer_done, adap->timeout);
> +	time_left = wait_for_completion_timeout(&id->xfer_done, msg_timeout);
>   	if (time_left == 0) {
>   		cdns_i2c_master_reset(adap);
>   		dev_err(id->adap.dev.parent,


If my assumption is right and there is any actual issue you had please send v2 
and feel free to add there my:
Acked-by: Michal Simek <michal.simek@xilinx.com>

Thanks,
Michal



  reply	other threads:[~2022-03-21 15:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09  9:31 [PATCH] i2c: cadence: Increase timeout per message if necessary Lucas Tanure
2022-03-21 15:57 ` Michal Simek [this message]
2022-03-22 15:34   ` tanureal
2022-03-22 17:18     ` Michal Simek
2022-03-23 10:07       ` tanureal
2022-03-23 11:02         ` Michal Simek

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=dd26fa4a-870e-d969-04df-1f42487e2b54@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=shubhrajyoti.datta@xilinx.com \
    --cc=tanureal@opensource.cirrus.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;
as well as URLs for NNTP newsgroup(s).