[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170714071800.GA1498@katana>
Date: Fri, 14 Jul 2017 09:18:00 +0200
From: Wolfram Sang <wsa@...-dreams.de>
To: Brendan Higgins <brendanhiggins@...gle.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Greg KH <gregkh@...uxfoundation.org>,
"David S . Miller" <davem@...emloft.net>, mchehab@...nel.org,
Joel Stanley <joel@....id.au>, martin.petersen@...cle.com,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
linux-i2c@...r.kernel.org, devicetree <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
OpenBMC Maillist <openbmc@...ts.ozlabs.org>
Subject: Re: [PATCH v11 3/4] i2c: aspeed: added driver for Aspeed I2C
> Basically what I was asking is whether I could use i2c_generic_scl_recovery
> in the case where SCL is hung.
The name is a bit misleading, I am afraid. Recovery can only be used when
SDA is stuck low. And to fix this it *uses* SCL toggling to get out of
it. And 'generic_scl' means 'gimme some SCL to control and I will toggle
it'. Compared to 'gpio_recovery' which will do all the GPIO handling for
you.
When SCL is hung, you can only reset the device which forces SCL low.
> I think I have a pretty good idea of what to do, I should probably just put
> together an RFC patch.
Sure.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists