Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1436092 > unrolled thread

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

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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

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

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

> +	/*
> +	 * 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?

[toc] | [next] | [standalone]

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

[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.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web