[PATCH 3/7] i2c: export bit-banging algo functions

2012-02-28 Thread Jean Delvare
On Mon, 27 Feb 2012 23:52:23 +0100, Daniel Vetter wrote: > On Mon, Feb 27, 2012 at 11:20:40PM +0100, Jean Delvare wrote: > > If you need to hot-switch between hardware and bit-banged I2C, I suggest > > that you lock the bus while doing so, to avoid switching while a > > transaction is in progress.

Re: [PATCH 3/7] i2c: export bit-banging algo functions

2012-02-28 Thread Jean Delvare
On Mon, 27 Feb 2012 23:52:23 +0100, Daniel Vetter wrote: > On Mon, Feb 27, 2012 at 11:20:40PM +0100, Jean Delvare wrote: > > If you need to hot-switch between hardware and bit-banged I2C, I suggest > > that you lock the bus while doing so, to avoid switching while a > > transaction is in progress.

[PATCH 3/7] i2c: export bit-banging algo functions

2012-02-27 Thread Daniel Vetter
On Mon, Feb 27, 2012 at 11:20:40PM +0100, Jean Delvare wrote: > Hi Daniel, > > Sorry for the late reply. > > On Tue, 14 Feb 2012 22:37:21 +0100, Daniel Vetter wrote: > > i915 has a hw i2c controller (gmbus) but for a bunch of stupid reasons > > we need to be able to fall back to the bit-banging a

[PATCH 3/7] i2c: export bit-banging algo functions

2012-02-27 Thread Jean Delvare
Hi Daniel, Sorry for the late reply. On Tue, 14 Feb 2012 22:37:21 +0100, Daniel Vetter wrote: > i915 has a hw i2c controller (gmbus) but for a bunch of stupid reasons > we need to be able to fall back to the bit-banging algo on gpio pins. > > The current code sets up a 2nd i2c controller for the

[PATCH 3/7] i2c: export bit-banging algo functions

2012-02-27 Thread Daniel Vetter
Hi Jean, Can you please review and if you don't have any objectsion, ack this patch for merging through drm-intel-next? Imo that's the easiest way to merge this series. Thanks, Daniel On Tue, Feb 14, 2012 at 10:37:21PM +0100, Daniel Vetter wrote: > i915 has a hw i2c controller (gmbus) but for a

Re: [PATCH 3/7] i2c: export bit-banging algo functions

2012-02-27 Thread Daniel Vetter
On Mon, Feb 27, 2012 at 11:20:40PM +0100, Jean Delvare wrote: > Hi Daniel, > > Sorry for the late reply. > > On Tue, 14 Feb 2012 22:37:21 +0100, Daniel Vetter wrote: > > i915 has a hw i2c controller (gmbus) but for a bunch of stupid reasons > > we need to be able to fall back to the bit-banging a

Re: [PATCH 3/7] i2c: export bit-banging algo functions

2012-02-27 Thread Jean Delvare
Hi Daniel, Sorry for the late reply. On Tue, 14 Feb 2012 22:37:21 +0100, Daniel Vetter wrote: > i915 has a hw i2c controller (gmbus) but for a bunch of stupid reasons > we need to be able to fall back to the bit-banging algo on gpio pins. > > The current code sets up a 2nd i2c controller for the

Re: [PATCH 3/7] i2c: export bit-banging algo functions

2012-02-27 Thread Daniel Vetter
Hi Jean, Can you please review and if you don't have any objectsion, ack this patch for merging through drm-intel-next? Imo that's the easiest way to merge this series. Thanks, Daniel On Tue, Feb 14, 2012 at 10:37:21PM +0100, Daniel Vetter wrote: > i915 has a hw i2c controller (gmbus) but for a

[PATCH 3/7] i2c: export bit-banging algo functions

2012-02-14 Thread Daniel Vetter
i915 has a hw i2c controller (gmbus) but for a bunch of stupid reasons we need to be able to fall back to the bit-banging algo on gpio pins. The current code sets up a 2nd i2c controller for the same i2c bus using the bit-banging algo. This has a bunch of issues, the major one being that userspace

[PATCH 3/7] i2c: export bit-banging algo functions

2012-02-14 Thread Daniel Vetter
i915 has a hw i2c controller (gmbus) but for a bunch of stupid reasons we need to be able to fall back to the bit-banging algo on gpio pins. The current code sets up a 2nd i2c controller for the same i2c bus using the bit-banging algo. This has a bunch of issues, the major one being that userspace