All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Tyrone Ting <warp5tw@gmail.com>
Cc: avifishman70@gmail.com, tmaimon77@gmail.com,
	tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
	benjaminfair@google.com, andi.shyti@kernel.org, wsa@kernel.org,
	rand.sec96@gmail.com, wsa+renesas@sang-engineering.com,
	tali.perry@nuvoton.com, Avi.Fishman@nuvoton.com,
	tomer.maimon@nuvoton.com, KWLIU@nuvoton.com, JJLIU0@nuvoton.com,
	kfting@nuvoton.com, openbmc@lists.ozlabs.org,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/6] i2c: npcm: Modify timeout evaluation mechanism
Date: Tue, 1 Oct 2024 16:14:03 +0300	[thread overview]
Message-ID: <Zvv1m3RT916dyYRC@smile.fi.intel.com> (raw)
In-Reply-To: <20241001062855.6928-4-kfting@nuvoton.com>

On Tue, Oct 01, 2024 at 02:28:52PM +0800, Tyrone Ting wrote:
> From: Tyrone Ting <kfting@nuvoton.com>
> 
> The users want to connect a lot of masters on the same bus.
> This timeout is used to determine the time it takes to take bus ownership.
> The transactions are very long, so waiting 35ms is not enough.
> 
> Increase the timeout and treat it as the total timeout, including retries.
> The total timeout is 2 seconds now.
> 
> The i2c core layer will have chances to retry to call the i2c driver
> transfer function if the i2c driver reports that the bus is busy and
> returns EAGAIN.

-EAGAIN

...

> +		/*
> +		 * Adaptive TimeOut: estimated time in usec + 100% margin:
> +		 * 2: double the timeout for clock stretching case
> +		 * 9: bits per transaction (including the ack/nack)
> +		 */
> +		timeout_usec = (2 * 9 * USEC_PER_SEC / bus->bus_freq) * (2 + nread + nwrite);

Side note (as I see it was in the original code), from physics
point of view the USEC_PER_SEC here should be simply MICRO
(as 1/Hz == s, and here it will be read as s^2 in the result),
but if one finds the current more understandable, okay then.

-- 
With Best Regards,
Andy Shevchenko



WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Tyrone Ting <warp5tw@gmail.com>
Cc: KWLIU@nuvoton.com, tomer.maimon@nuvoton.com,
	linux-kernel@vger.kernel.org, benjaminfair@google.com,
	wsa+renesas@sang-engineering.com, avifishman70@gmail.com,
	venture@google.com, openbmc@lists.ozlabs.org, kfting@nuvoton.com,
	JJLIU0@nuvoton.com, tali.perry@nuvoton.com,
	tali.perry1@gmail.com, wsa@kernel.org, andi.shyti@kernel.org,
	linux-i2c@vger.kernel.org, Avi.Fishman@nuvoton.com,
	rand.sec96@gmail.com, tmaimon77@gmail.com
Subject: Re: [PATCH v5 3/6] i2c: npcm: Modify timeout evaluation mechanism
Date: Tue, 1 Oct 2024 16:14:03 +0300	[thread overview]
Message-ID: <Zvv1m3RT916dyYRC@smile.fi.intel.com> (raw)
In-Reply-To: <20241001062855.6928-4-kfting@nuvoton.com>

On Tue, Oct 01, 2024 at 02:28:52PM +0800, Tyrone Ting wrote:
> From: Tyrone Ting <kfting@nuvoton.com>
> 
> The users want to connect a lot of masters on the same bus.
> This timeout is used to determine the time it takes to take bus ownership.
> The transactions are very long, so waiting 35ms is not enough.
> 
> Increase the timeout and treat it as the total timeout, including retries.
> The total timeout is 2 seconds now.
> 
> The i2c core layer will have chances to retry to call the i2c driver
> transfer function if the i2c driver reports that the bus is busy and
> returns EAGAIN.

-EAGAIN

...

> +		/*
> +		 * Adaptive TimeOut: estimated time in usec + 100% margin:
> +		 * 2: double the timeout for clock stretching case
> +		 * 9: bits per transaction (including the ack/nack)
> +		 */
> +		timeout_usec = (2 * 9 * USEC_PER_SEC / bus->bus_freq) * (2 + nread + nwrite);

Side note (as I see it was in the original code), from physics
point of view the USEC_PER_SEC here should be simply MICRO
(as 1/Hz == s, and here it will be read as s^2 in the result),
but if one finds the current more understandable, okay then.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-10-01 13:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01  6:28 [PATCH v5 0/6] i2c: npcm: read/write operation, checkpatch Tyrone Ting
2024-10-01  6:28 ` [PATCH v5 1/6] i2c: npcm: correct the read/write operation procedure Tyrone Ting
2024-10-01  6:28 ` [PATCH v5 2/6] i2c: npcm: use a software flag to indicate a BER condition Tyrone Ting
2024-10-01  6:28 ` [PATCH v5 3/6] i2c: npcm: Modify timeout evaluation mechanism Tyrone Ting
2024-10-01 13:14   ` Andy Shevchenko [this message]
2024-10-01 13:14     ` Andy Shevchenko
2024-10-09  5:49     ` Tyrone Ting
2024-10-09  5:49       ` Tyrone Ting
2024-10-01  6:28 ` [PATCH v5 4/6] i2c: npcm: Modify the client address assignment Tyrone Ting
2024-10-01 13:17   ` Andy Shevchenko
2024-10-01 13:17     ` Andy Shevchenko
2024-10-04  1:49     ` Tyrone Ting
2024-10-04  1:49       ` Tyrone Ting
2024-10-04  2:29       ` Tyrone Ting
2024-10-04  2:29         ` Tyrone Ting
2024-10-08  1:41         ` Tyrone Ting
2024-10-08  1:41           ` Tyrone Ting
2024-10-08 16:21         ` Andy Shevchenko
2024-10-08 16:21           ` Andy Shevchenko
2024-10-09  5:48           ` Tyrone Ting
2024-10-09  5:48             ` Tyrone Ting
2024-10-01  6:28 ` [PATCH v5 5/6] i2c: npcm: use i2c frequency table Tyrone Ting
2024-10-01 13:23   ` Andy Shevchenko
2024-10-01 13:23     ` Andy Shevchenko
2024-10-04  1:51     ` Tyrone Ting
2024-10-04  1:51       ` Tyrone Ting
2024-10-01  6:28 ` [PATCH v5 6/6] i2c: npcm: Enable slave in eob interrupt Tyrone Ting
2024-10-01  6:28   ` Tyrone Ting
2024-10-02  8:34 ` [PATCH v5 0/6] i2c: npcm: read/write operation, checkpatch Andi Shyti
2024-10-02  8:34   ` Andi Shyti
2024-10-04  1:44   ` Tyrone Ting
2024-10-04  1:44     ` Tyrone Ting

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=Zvv1m3RT916dyYRC@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Avi.Fishman@nuvoton.com \
    --cc=JJLIU0@nuvoton.com \
    --cc=KWLIU@nuvoton.com \
    --cc=andi.shyti@kernel.org \
    --cc=avifishman70@gmail.com \
    --cc=benjaminfair@google.com \
    --cc=kfting@nuvoton.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=rand.sec96@gmail.com \
    --cc=tali.perry1@gmail.com \
    --cc=tali.perry@nuvoton.com \
    --cc=tmaimon77@gmail.com \
    --cc=tomer.maimon@nuvoton.com \
    --cc=venture@google.com \
    --cc=warp5tw@gmail.com \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@kernel.org \
    --cc=yuenn@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.