All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: BUG: bttv does not load module ir-kbd-i2c for Hauppauge model 37284, rev B421
Date: Tue, 08 Jan 2013 18:46:08 +0100	[thread overview]
Message-ID: <50EC5B60.7000207@googlemail.com> (raw)
In-Reply-To: <20130107142938.6e8f2c73@redhat.com>

<snip>
>
>>> It probably makes sense to add a "has_ir_i2c" field at bttv, add a flag
>>> there at modprobe to prevent the autoload, and start tagging the boards
>>> with I2C IR with such tag.
>> Without having looked into the code, it seems that the driver detects
>> the i2c rc already without a board flag.
>> Otherwise it wouldn't register the i2c device. Unfortunately, it doesn't
>> display a message.
> No. In the past (kernel 2.4 and upper), I2C bus used to work with 0-len
> reads to scan the used I2C addresses. The I2C drivers like tuners, demods,
> IR's etc used to register to the I2C core saying that they were to be used
> on TV boards. The I2C logic binds them to the I2C bus driver when they were
> detected, during the scanning process.
>
> That's why it is so hard to know what boards are using I2C remotes, on
> those older drivers.

Hmmm... so the I2C subystem probes a list of addresses and just
registers all devices it finds, but the driver itself doesn't know if
one of them is a RC device ?
Sounds odd. Will have to check the code to understand what's going on...

Regards,
Frank


      reply	other threads:[~2013-01-08 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 14:00 BUG: bttv does not load module ir-kbd-i2c for Hauppauge model 37284, rev B421 Frank Schäfer
2013-01-05 15:57 ` Mauro Carvalho Chehab
2013-01-06 20:36   ` Frank Schäfer
2013-01-07 16:29     ` Mauro Carvalho Chehab
2013-01-08 17:46       ` Frank Schäfer [this message]

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=50EC5B60.7000207@googlemail.com \
    --to=fschaefer.oss@googlemail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.