Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-17 Thread Trent Piepho
On Tue, 17 Mar 2009, Jean Delvare wrote: On Mon, 16 Mar 2009 15:47:17 -0700 (PDT), Trent Piepho wrote: On Mon, 16 Mar 2009, Jean Delvare wrote: You are unfair. The pull request came with a short log of all the changes. short log. His entire series was decribed with fewer words than I

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Jean Delvare
Hi Trent, On Sun, 15 Mar 2009 16:46:36 -0700 (PDT), Trent Piepho wrote: On Sun, 15 Mar 2009, Andy Walls wrote: But the specific problem that Hans' brings up is precisely a Linux kernel I2C subsystem *software* prohibition on two i2c_clients binding to the same address on the same adapter.

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Mauro Carvalho Chehab
On Sun, 15 Mar 2009 18:53:13 +0100 Jean Delvare kh...@linux-fr.org wrote: On Sun, 15 Mar 2009 10:42:41 -0700 (PDT), Trent Piepho wrote: On Sun, 15 Mar 2009, Jean Delvare wrote: On Sun, 15 Mar 2009 13:44:01 +0100, Hans Verkuil wrote: This is the typical multifunction device problem. It

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Mauro Carvalho Chehab
On Sun, 15 Mar 2009 18:53:13 +0100 Jean Delvare kh...@linux-fr.org wrote: On Sun, 15 Mar 2009 10:42:41 -0700 (PDT), Trent Piepho wrote: On Sun, 15 Mar 2009, Jean Delvare wrote: On Sun, 15 Mar 2009 13:44:01 +0100, Hans Verkuil wrote: This is the typical multifunction device problem. It

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Jean Delvare
Hi Mauro, On Mon, 16 Mar 2009 06:34:02 -0300, Mauro Carvalho Chehab wrote: On Sun, 15 Mar 2009 18:53:13 +0100 Jean Delvare kh...@linux-fr.org wrote: On Sun, 15 Mar 2009 10:42:41 -0700 (PDT), Trent Piepho wrote: You can also split the device into multiple devices. Most SoCs have one

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Andy Walls
On Sun, 2009-03-15 at 13:44 +0100, Hans Verkuil wrote: Hi Mauro, Jean, When converting the bttv driver to v4l2_subdev I found one probing conflict between tvaudio and ir-kbd-i2c: address 0x96 (or 0x4b in 7-bit notation). It turns out that this is one and the same PIC16C54 device used on

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Hans Verkuil
On Sun, 2009-03-15 at 13:44 +0100, Hans Verkuil wrote: Hi Mauro, Jean, When converting the bttv driver to v4l2_subdev I found one probing conflict between tvaudio and ir-kbd-i2c: address 0x96 (or 0x4b in 7-bit notation). It turns out that this is one and the same PIC16C54 device used on

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Mauro Carvalho Chehab
On Mon, 16 Mar 2009 12:18:01 +0100 Jean Delvare kh...@linux-fr.org wrote: With the current approach, we need to bind two completely different things inside the same i2c module, which may result in a very poor design. I really don't see any problem there. There are many drivers (i2c or

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Jean Delvare
Hi Mauro, On Mon, 16 Mar 2009 09:52:37 -0300, Mauro Carvalho Chehab wrote: On Mon, 16 Mar 2009 12:18:01 +0100 Jean Delvare kh...@linux-fr.org wrote: I really don't see any problem there. There are many drivers (i2c or not) in the kernel which do exactly this and this works just fine. We

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Mauro Carvalho Chehab
I need to be short, since I'm about to travel. On Mon, 16 Mar 2009 15:28:02 +0100 Jean Delvare kh...@linux-fr.org wrote: Ah yeah, now I remember. You're the one who considers 2.6.18 a bleeding edge kernel suitable for upstream development. This explains a lot. I have 3 separated

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Hans Verkuil
On Monday 16 March 2009 22:40:40 Jean Delvare wrote: On Mon, 16 Mar 2009 12:43:33 -0700 (PDT), Trent Piepho wrote: On Mon, 16 Mar 2009, Jean Delvare wrote: Come on, just look at ir-kbd-i2c and tvaudio again, see how great are these drivers which have been designed on top of the legacy i2c

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-16 Thread Trent Piepho
On Mon, 16 Mar 2009, Jean Delvare wrote: On Mon, 16 Mar 2009 12:43:33 -0700 (PDT), Trent Piepho wrote: On Mon, 16 Mar 2009, Jean Delvare wrote: Come on, just look at ir-kbd-i2c and tvaudio again, see how great are these drivers which have been designed on top of the legacy i2c binding

bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-15 Thread Hans Verkuil
Hi Mauro, Jean, When converting the bttv driver to v4l2_subdev I found one probing conflict between tvaudio and ir-kbd-i2c: address 0x96 (or 0x4b in 7-bit notation). It turns out that this is one and the same PIC16C54 device used on the ProVideo PV951 board. This chip is used for both audio

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-15 Thread Jean Delvare
Hi Hans, On Sun, 15 Mar 2009 13:44:01 +0100, Hans Verkuil wrote: Hi Mauro, Jean, When converting the bttv driver to v4l2_subdev I found one probing conflict between tvaudio and ir-kbd-i2c: address 0x96 (or 0x4b in 7-bit notation). It turns out that this is one and the same PIC16C54

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-15 Thread Trent Piepho
On Sun, 15 Mar 2009, Jean Delvare wrote: On Sun, 15 Mar 2009 13:44:01 +0100, Hans Verkuil wrote: This is the typical multifunction device problem. It isn't specifically related to I2C, the exact same problem happens for other devices, for example a PCI south bridge including hardware

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-15 Thread Jean Delvare
On Sun, 15 Mar 2009 10:42:41 -0700 (PDT), Trent Piepho wrote: On Sun, 15 Mar 2009, Jean Delvare wrote: On Sun, 15 Mar 2009 13:44:01 +0100, Hans Verkuil wrote: This is the typical multifunction device problem. It isn't specifically related to I2C, the exact same problem happens for other

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-15 Thread Hans Verkuil
On Sunday 15 March 2009 20:34:33 Andy Walls wrote: On Sun, 2009-03-15 at 18:12 +0100, Jean Delvare wrote: Hi Hans, On Sun, 15 Mar 2009 13:44:01 +0100, Hans Verkuil wrote: Hi Mauro, Jean, When converting the bttv driver to v4l2_subdev I found one probing conflict between tvaudio

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-15 Thread Jean Delvare
Hi Andy, On Sun, 15 Mar 2009 15:34:33 -0400, Andy Walls wrote: On Sun, 2009-03-15 at 18:12 +0100, Jean Delvare wrote: Hi Hans, On Sun, 15 Mar 2009 13:44:01 +0100, Hans Verkuil wrote: Hi Mauro, Jean, When converting the bttv driver to v4l2_subdev I found one probing conflict

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-15 Thread Jean Delvare
On Sun, 15 Mar 2009 23:09:05 +0100, Hans Verkuil wrote: Actually, it seems like this used to work at one time in the past. Jean, can you confirm that it used to be possible to have two i2c clients at the same i2c address in the past? Looking at the post (see the link in my original mail) it

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-15 Thread Trent Piepho
On Sun, 15 Mar 2009, Andy Walls wrote: On Sun, 2009-03-15 at 18:12 +0100, Jean Delvare wrote: This is the typical multifunction device problem. It isn't specifically related to I2C, But the specific problem that Hans' brings up is precisely a Linux kernel I2C subsystem *software*

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-15 Thread Andy Walls
On Sun, 2009-03-15 at 23:26 +0100, Jean Delvare wrote: Hi Andy, Hi Jean, Thanks for the reply. On Sun, 15 Mar 2009 15:34:33 -0400, Andy Walls wrote: On Sun, 2009-03-15 at 18:12 +0100, Jean Delvare wrote: Hi Hans, This is the typical multifunction device problem. It isn't specifically

Re: bttv, tvaudio and ir-kbd-i2c probing conflict

2009-03-15 Thread hermann pitton
Hi, Am Sonntag, den 15.03.2009, 20:52 -0400 schrieb Andy Walls: On Sun, 2009-03-15 at 23:26 +0100, Jean Delvare wrote: Hi Andy, Hi Jean, Thanks for the reply. On Sun, 15 Mar 2009 15:34:33 -0400, Andy Walls wrote: On Sun, 2009-03-15 at 18:12 +0100, Jean Delvare wrote: Hi Hans,