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

From	Eric Anholt <eric@anholt.net>
Newsgroups	linux.kernel
Subject	Re: [PATCH] i2c: bcm2835: Set up the clock stretching timeout at boot.
Date	2016-07-04 03:10 +0200
Message-ID	<rR0yB-7ya-1@gated-at.bofh.it> (permalink)
References	<rFmuR-60k-1@gated-at.bofh.it> <rR05z-78B-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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

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.

Back to linux.kernel | Previous | Next — Previous in thread | 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-04 02:40 +0200
  Re: [PATCH] i2c: bcm2835: Set up the clock stretching timeout at boot. Eric Anholt <eric@anholt.net> - 2016-07-04 03:10 +0200

csiph-web