public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Mike Isely <isely@pobox.com>
Cc: isely@isely.net, LMML <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH 2/6] ir-kbd-i2c: Switch to the new-style device binding model
Date: Sat, 18 Apr 2009 15:16:25 +0200	[thread overview]
Message-ID: <20090418151625.254e466b@hyperion.delvare> (raw)
In-Reply-To: <20090418112519.774e0dae@hyperion.delvare>

Hi again Mike,

On Sat, 18 Apr 2009 11:25:19 +0200, Jean Delvare wrote:
> On Fri, 17 Apr 2009 18:35:55 -0500 (CDT), Mike Isely wrote:
> > I thought we were going to leave the pvrusb2 driver out of this since 
> > I've already got a change ready that also includes additional logic to 
> > take into account the properties of the hardware device (i.e. only 
> > activate ir-kbd-i2c when we know it has a chance of working).
> 
> Hmm, I thought that our latest discussions had (at least partly)
> obsoleted your patches. Remember that we want to always instantiate
> ir_video I2C devices even when ir-kbd-i2c can't driver them, otherwise
> lirc won't be able to bind to the devices in question as soon as the
> legacy binding model is gone. So the conditionals in your second patch
> (which is all that makes it differ from mine) are no longer desirable.
> 
> I'll work on lirc patches today or tomorrow, so that lirc doesn't break
> when my patches hit mainline.

Speaking of this: do you know all the I2C addresses that can host IR
devices on pvrusb2 cards? I understand that the only address supported
by ir-kbd-i2c is 0x18, but I also need to know the addresses supported
by lirc_i2c and possibly lirc_zilog, if you happen to know this.

Thanks,
-- 
Jean Delvare

  reply	other threads:[~2009-04-18 13:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 20:29 [PATCH 0/6] ir-kbd-i2c conversion to the new i2c binding model (v2) Jean Delvare
2009-04-17 20:30 ` [PATCH 1/6] ir-kbd-i2c: Don't use i2c_client.name for our own needs Jean Delvare
2009-04-17 20:31 ` [PATCH 2/6] ir-kbd-i2c: Switch to the new-style device binding model Jean Delvare
2009-04-17 23:35   ` Mike Isely
2009-04-18  9:25     ` Jean Delvare
2009-04-18 13:16       ` Jean Delvare [this message]
2009-04-18 13:53         ` Mike Isely
2009-04-23  9:00           ` Jean Delvare
2009-04-24  2:44             ` Mike Isely
2009-05-02  1:30               ` Mike Isely
2009-05-02  7:12                 ` Jean Delvare
2009-05-11  8:17                   ` Mauro Carvalho Chehab
2009-04-17 20:32 ` [PATCH 3/6] ir-kbd-i2c: Use initialization data Jean Delvare
2009-04-17 20:32 ` [PATCH 4/6] ir-kbd-i2c: Don't assume all IR receivers are supported Jean Delvare
2009-04-17 20:33 ` [PATCH 5/6] saa7134: Simplify handling of IR on MSI TV@nywhere Plus Jean Delvare
2009-04-17 20:34 ` [PATCH 6/6] saa7134: Simplify handling of IR on AVerMedia Cardbus E506R Jean Delvare
2009-04-29 12:29 ` [PATCH 0/6] ir-kbd-i2c conversion to the new i2c binding model (v2) Jean Delvare
2009-04-29 22:40   ` hermann pitton
2009-04-30  2:58   ` Devin Heitmueller

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=20090418151625.254e466b@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=isely@isely.net \
    --cc=isely@pobox.com \
    --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