Hi Jean,
On Tue, Jun 08, 2010 at 10:01:00AM +0200, Jean Delvare wrote:
Now that i2c-core offers the possibility to provide custom probing
function for I2C devices, let's make use of it.
Signed-off-by: Jean Delvare kh...@linux-fr.org
Acked-by: Mauro Carvalho Chehab mche...@redhat.com
If
Hi Andy,
On Sun, 04 Apr 2010 21:54:39 -0400, Andy Walls wrote:
On Sun, 2010-04-04 at 16:14 +0200, Jean Delvare wrote:
Now that i2c-core offers the possibility to provide custom probing
function for I2C devices, let's make use of it.
Signed-off-by: Jean Delvare kh...@linux-fr.org
---
Hi Jean,
Jean Delvare wrote:
Now that i2c-core offers the possibility to provide custom probing
function for I2C devices, let's make use of it.
Signed-off-by: Jean Delvare kh...@linux-fr.org
---
I wasn't too sure where to put the custom probe function: in each driver,
in the ir-common
Hi Mauro,
On Mon, 05 Apr 2010 15:26:32 -0300, Mauro Carvalho Chehab wrote:
Jean Delvare wrote:
Now that i2c-core offers the possibility to provide custom probing
function for I2C devices, let's make use of it.
Signed-off-by: Jean Delvare kh...@linux-fr.org
---
I wasn't too sure
Jean Delvare wrote:
Hi Mauro,
On Mon, 05 Apr 2010 15:26:32 -0300, Mauro Carvalho Chehab wrote:
Jean Delvare wrote:
Now that i2c-core offers the possibility to provide custom probing
function for I2C devices, let's make use of it.
Signed-off-by: Jean Delvare kh...@linux-fr.org
---
I
Now that i2c-core offers the possibility to provide custom probing
function for I2C devices, let's make use of it.
Signed-off-by: Jean Delvare kh...@linux-fr.org
---
I wasn't too sure where to put the custom probe function: in each driver,
in the ir-common module or in the v4l2-common module. I
On Sun, 2010-04-04 at 16:14 +0200, Jean Delvare wrote:
Now that i2c-core offers the possibility to provide custom probing
function for I2C devices, let's make use of it.
Signed-off-by: Jean Delvare kh...@linux-fr.org
---
I wasn't too sure where to put the custom probe function: in each
Hi Matthieu,
On Sun, 21 Mar 2010 15:22:00 +0100, matthieu castet wrote:
Do you know why there is 2 methods of probing i2c [1] and [2], with different
quirks for eeprom.
Historical reasons, mainly. i2c_detect() is an old thing, it is used by
device drivers which want to automatically probe for
Hi,
Do you know why there is 2 methods of probing i2c [1] and [2], with different
quirks for eeprom.
Why can't they be merged together ?
Thanks
Matthieu
PS : please keep me in CC
[1]
i2c_detect_address
/* Make sure the address is valid */
if (addr 0x03 || addr 0x77) {
