Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1448441 > unrolled thread
| Started by | Wolfram Sang <wsa@the-dreams.de> |
|---|---|
| First post | 2016-07-22 09:30 +0200 |
| Last post | 2016-07-22 09:30 +0200 |
| Articles | 1 — 1 participant |
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.
Re: [PATCH] i2c: bcm2835: Set up the clock stretching timeout at boot. Wolfram Sang <wsa@the-dreams.de> - 2016-07-22 09:30 +0200
| From | Wolfram Sang <wsa@the-dreams.de> |
|---|---|
| Date | 2016-07-22 09:30 +0200 |
| Subject | Re: [PATCH] i2c: bcm2835: Set up the clock stretching timeout at boot. |
| Message-ID | <rXD4e-2FR-17@gated-at.bofh.it> |
[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 top | Article view | linux.kernel
csiph-web