From: Hans Verkuil <hverkuil@xs4all.nl>
To: linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Jean Delvare <khali@linux-fr.org>
Subject: bttv, tvaudio and ir-kbd-i2c probing conflict
Date: Sun, 15 Mar 2009 13:44:01 +0100 [thread overview]
Message-ID: <200903151344.01730.hverkuil@xs4all.nl> (raw)
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 input selection and
for IR handling.
But the tvaudio module does the audio part and the ir-kbd-i2c module does
the IR part. I have truly no idea how this should be handled in the new
situation. For that matter, I wonder whether it ever worked at all since my
understanding is that once you called i2c_attach_client for a particular
address, you cannot do that a second time. So depending on which module
happens to register itself first, you either have working audio or working
IR, but not both.
It might work if you use lirc, since that uses low-level i2c access
(right?). But I can't see how it can work with ir-kbd-i2c and tvaudio at
the same time.
Did some googling and this seems to confirm my analysis:
http://lists.zerezo.com/video4linux/msg21328.html
Ideas on a postcard, please... :-)
Regards,
Hans
--
Hans Verkuil - video4linux developer - sponsored by TANDBERG
next reply other threads:[~2009-03-15 12:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 12:44 Hans Verkuil [this message]
2009-03-15 17:12 ` bttv, tvaudio and ir-kbd-i2c probing conflict Jean Delvare
2009-03-15 17:42 ` Trent Piepho
2009-03-15 17:53 ` Jean Delvare
2009-03-16 9:08 ` Mauro Carvalho Chehab
2009-03-16 9:34 ` Mauro Carvalho Chehab
2009-03-16 11:18 ` Jean Delvare
2009-03-16 12:52 ` Mauro Carvalho Chehab
2009-03-16 14:28 ` Jean Delvare
2009-03-16 15:31 ` Mauro Carvalho Chehab
2009-03-16 19:43 ` Trent Piepho
2009-03-16 21:40 ` Jean Delvare
2009-03-16 21:58 ` Hans Verkuil
2009-03-16 22:47 ` Trent Piepho
2009-03-17 9:31 ` Jean Delvare
2009-03-17 20:23 ` Trent Piepho
2009-03-15 19:34 ` Andy Walls
2009-03-15 22:09 ` Hans Verkuil
2009-03-15 22:28 ` Jean Delvare
2009-03-15 22:26 ` Jean Delvare
2009-03-16 0:52 ` Andy Walls
2009-03-16 4:26 ` hermann pitton
2009-03-16 12:58 ` Jean Delvare
2009-03-15 23:46 ` Trent Piepho
2009-03-16 8:35 ` Jean Delvare
2009-03-16 11:35 ` Andy Walls
-- strict thread matches above, loose matches on Subject: below --
2009-03-16 11:56 Hans Verkuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903151344.01730.hverkuil@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=khali@linux-fr.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox