On Tue, Apr 16, 2013 at 09:34:58AM -0700, Olof Johansson wrote:
> Overdue, should have added a few iterations ago: :)
Why is that? Is the current iteration too generic for your taste?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Tue, Apr 16, 2013 at 09:29:00AM -0700, Doug Anderson wrote:
> The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
> where masters need to claim the bus with a GPIO before they can start
> a transcation. This should generally only be used when standard I2C
> multimaster isn't
On Tue, Apr 16, 2013 at 09:29:00AM -0700, Doug Anderson wrote:
The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
where masters need to claim the bus with a GPIO before they can start
a transcation. This should generally only be used when standard I2C
multimaster isn't
On Tue, Apr 16, 2013 at 09:34:58AM -0700, Olof Johansson wrote:
Overdue, should have added a few iterations ago: :)
Why is that? Is the current iteration too generic for your taste?
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Tue, Apr 16, 2013 at 09:29:00AM -0700, Doug Anderson wrote:
> The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
> where masters need to claim the bus with a GPIO before they can start
> a transcation. This should generally only be used when standard I2C
I am having fun
Overdue, should have added a few iterations ago: :)
On Tue, Apr 16, 2013 at 09:29:00AM -0700, Doug Anderson wrote:
> The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
> where masters need to claim the bus with a GPIO before they can start
> a transcation. This should
The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
where masters need to claim the bus with a GPIO before they can start
a transcation. This should generally only be used when standard I2C
multimaster isn't appropriate for some reason (errata/bugs).
This driver is based on
The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
where masters need to claim the bus with a GPIO before they can start
a transcation. This should generally only be used when standard I2C
multimaster isn't appropriate for some reason (errata/bugs).
This driver is based on
Overdue, should have added a few iterations ago: :)
On Tue, Apr 16, 2013 at 09:29:00AM -0700, Doug Anderson wrote:
The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
where masters need to claim the bus with a GPIO before they can start
a transcation. This should generally
On Tue, Apr 16, 2013 at 09:29:00AM -0700, Doug Anderson wrote:
The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
where masters need to claim the bus with a GPIO before they can start
a transcation. This should generally only be used when standard I2C
I am having fun with
10 matches
Mail list logo