Re: [PATCH] i2c: bcm2835: Set up the clock stretching timeout at boot.

From	Wolfram Sang <wsa@the-dreams.de>
Newsgroups	linux.kernel
Subject	Re: [PATCH] i2c: bcm2835: Set up the clock stretching timeout at boot.
Date	2016-07-22 09:30 +0200
Message-ID	<rXD4e-2FR-17@gated-at.bofh.it> (permalink)
References	<rFmuR-60k-1@gated-at.bofh.it> <rR05z-78B-9@gated-at.bofh.it> <rR0yB-7ya-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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?

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [PATCH] i2c: bcm2835: Set up the clock stretching timeout at  boot. Wolfram Sang <wsa@the-dreams.de> - 2016-07-22 09:30 +0200

csiph-web