From mboxrd@z Thu Jan 1 00:00:00 1970 From: eric@anholt.net (Eric Anholt) Date: Sun, 03 Jul 2016 18:02:32 -0700 Subject: [PATCH] i2c: bcm2835: Set up the clock stretching timeout at boot. In-Reply-To: <20160704003118.GA1381@tetsubishi> References: <1464818845-5348-1-git-send-email-eric@anholt.net> <20160704003118.GA1381@tetsubishi> Message-ID: <87lh1ip653.fsf@eliezer.anholt.net> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Wolfram Sang 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 818 bytes Desc: not available URL: