On Thu, Feb 19, 2015 at 12:06:49PM -0600, Felipe Balbi wrote:
If either SCL or SDA are stuck low, we need to
recover the bus using the procedure described
on section 3.1.16 of the I2C specification.
Note that we're trying to implement the procedure
exactly as described by that section.
On Wed, Mar 11, 2015 at 03:47:53PM +0200, Grygorii Strashko wrote:
Hi Felipe,
On 03/11/2015 03:50 AM, Felipe Balbi wrote:
On Mon, Mar 09, 2015 at 11:39:17AM -0500, Felipe Balbi wrote:
On Thu, Feb 19, 2015 at 12:06:49PM -0600, Felipe Balbi wrote:
If either SCL or SDA are stuck low, we need
Hi Felipe,
On 03/11/2015 03:50 AM, Felipe Balbi wrote:
On Mon, Mar 09, 2015 at 11:39:17AM -0500, Felipe Balbi wrote:
On Thu, Feb 19, 2015 at 12:06:49PM -0600, Felipe Balbi wrote:
If either SCL or SDA are stuck low, we need to
recover the bus using the procedure described
on section 3.1.16 of
On Mon, Mar 09, 2015 at 11:39:17AM -0500, Felipe Balbi wrote:
On Thu, Feb 19, 2015 at 12:06:49PM -0600, Felipe Balbi wrote:
If either SCL or SDA are stuck low, we need to
recover the bus using the procedure described
on section 3.1.16 of the I2C specification.
Note that we're trying to
On Thu, Feb 19, 2015 at 12:06:49PM -0600, Felipe Balbi wrote:
If either SCL or SDA are stuck low, we need to
recover the bus using the procedure described
on section 3.1.16 of the I2C specification.
Note that we're trying to implement the procedure
exactly as described by that section.
On Thu, Feb 19, 2015 at 12:06:49PM -0600, Felipe Balbi wrote:
If either SCL or SDA are stuck low, we need to
recover the bus using the procedure described
on section 3.1.16 of the I2C specification.
Note that we're trying to implement the procedure
exactly as described by that section.
If either SCL or SDA are stuck low, we need to
recover the bus using the procedure described
on section 3.1.16 of the I2C specification.
Note that we're trying to implement the procedure
exactly as described by that section. First we
check which line is stuck low, then implement
one or the other
