From: Wolfram Sang <wsa@the-dreams.de>
To: Eric Anholt <eric@anholt.net>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: bcm2835: Set up the clock stretching timeout at boot.
Date: Fri, 22 Jul 2016 09:27:40 +0200 [thread overview]
Message-ID: <20160722072740.GG1605@katana> (raw)
In-Reply-To: <87lh1ip653.fsf@eliezer.anholt.net>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
On Sun, Jul 03, 2016 at 06:02:32PM -0700, Eric Anholt wrote:
> Wolfram Sang <wsa@the-dreams.de> writes:
>
> >> + /*
> >> + * SMBUS says "Devices participating in a transfer will
> >> + * timeout when any clock low exceeds the value of
> >> + * T_TIMEOUT,MIN of 25 ms."
> >> + */
> >
> > SMBus has that timeout, but I2C doesn't. How about disabling the timeout
> > simply? Or using the max value if you want to keep the timeout
> > detection?
>
> Disabling the timeout seems fine to me. We still have a 1-second
> timeout around the entire transfer. I'll be back on my DSI branch this
> week and test it out then.
Did it work?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-22 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 22:07 [PATCH] i2c: bcm2835: Set up the clock stretching timeout at boot Eric Anholt
2016-06-02 16:35 ` Stefan Wahren
[not found] ` <25336b03-76d1-2466-fbc0-9f363d3e7638@i2se.com>
2016-06-02 18:02 ` Eric Anholt
2016-07-04 0:31 ` Wolfram Sang
2016-07-04 1:02 ` Eric Anholt
2016-07-22 7:27 ` Wolfram Sang [this message]
2016-10-03 19:50 ` Eric Anholt
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=20160722072740.GG1605@katana \
--to=wsa@the-dreams.de \
--cc=eric@anholt.net \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=swarren@wwwdotorg.org \
/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).