From: Wolfram Sang <wsa@the-dreams.de>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: "Eric Anholt" <eric@anholt.net>,
"Noralf Trønnes" <noralf@tronnes.org>,
linux-i2c@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] i2c: bcm2835: Avoid clock stretching timeouts
Date: Mon, 7 Feb 2022 16:08:53 +0100 [thread overview]
Message-ID: <YgE2BbZ29KDcClQO@shikoro> (raw)
In-Reply-To: <1519422151-6218-1-git-send-email-stefan.wahren@i2se.com>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
On Fri, Feb 23, 2018 at 10:42:31PM +0100, Stefan Wahren wrote:
> From: Eric Anholt <eric@anholt.net>
>
> The CLKT register contains at poweron 0x40, which at our typical 100kHz
> bus rate means .64ms. But there is no specified limit to how long devices
> should be able to stretch the clocks, so just disable the timeout. We
> still have a timeout wrapping the entire transfer.
>
> Signed-off-by: Eric Anholt <eric@anholt.net>
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
Okay, it has been years but the issue came up again [1] so finally
applied to for-current with stable added, thanks!
[1] http://patchwork.ozlabs.org/project/linux-i2c/patch/20220117102504.90585-1-iivanov@suse.de/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-02-07 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 21:42 [PATCH] i2c: bcm2835: Avoid clock stretching timeouts Stefan Wahren
2018-02-26 23:33 ` Eric Anholt
2022-02-07 15:08 ` Wolfram Sang [this message]
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=YgE2BbZ29KDcClQO@shikoro \
--to=wsa@the-dreams.de \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=noralf@tronnes.org \
--cc=stefan.wahren@i2se.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).