From: Jean Delvare <khali@linux-fr.org>
To: Andy Walls <awalls@radix.net>
Cc: linux-media@vger.kernel.org, Jarod Wilson <jarod@redhat.com>,
Mark Lord <lkml@rtr.ca>, Mike Isely <isely@pobox.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Janne Grunau <j@jannau.net>
Subject: Re: [PATCH 3/3] ir-kbd-i2c: Add support for Z8F0811/Hauppage IR transceivers
Date: Sun, 19 Jul 2009 21:22:06 +0200 [thread overview]
Message-ID: <20090719212206.593f9eeb@hyperion.delvare> (raw)
In-Reply-To: <1247863795.10066.36.camel@palomino.walls.org>
Hi Andy,
On Fri, 17 Jul 2009 16:49:55 -0400, Andy Walls wrote:
> This patch adds support for Zilog Z8F0811 IR transceiver chips on
> CX2341[68] based boards to ir-kbd-i2c for both the old i2c binding model
> and the new i2c binding model.
>
> Regards,
> Andy
>
> diff -r d754a2d5a376 linux/drivers/media/video/ir-kbd-i2c.c
> --- a/linux/drivers/media/video/ir-kbd-i2c.c Wed Jul 15 07:28:02 2009 -0300
> +++ b/linux/drivers/media/video/ir-kbd-i2c.c Fri Jul 17 16:05:28 2009 -0400
> @@ -442,9 +442,11 @@
> case 0x47:
> case 0x71:
> case 0x2d:
> - if (adap->id == I2C_HW_B_CX2388x) {
> + if (adap->id == I2C_HW_B_CX2388x ||
> + adap->id == I2C_HW_B_CX2341X) {
> /* Handled by cx88-input */
> - name = "CX2388x remote";
> + name = adap->id == I2C_HW_B_CX2341X ? "CX2341x remote"
> + : "CX2388x remote";
> ir_type = IR_TYPE_RC5;
> ir->get_key = get_key_haup_xvr;
> if (hauppauge == 1) {
> @@ -697,7 +726,8 @@
> static const struct i2c_device_id ir_kbd_id[] = {
> /* Generic entry for any IR receiver */
> { "ir_video", 0 },
> - /* IR device specific entries could be added here */
> + /* IR device specific entries should be added here */
> + { "ir_rx_z8f0811_haup", 0 },
> { }
> };
>
Yes, looks good.
--
Jean Delvare
prev parent reply other threads:[~2009-07-19 19:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 20:29 [PATCH 0/3] ir-kbd-i2c, cx18: IR devices for CX23418 boards Andy Walls
2009-07-17 20:35 ` [PATCH 1/3] ir-kbd-i2c: Allow use of ir-kdb-i2c internal get_key funcs and set ir_type Andy Walls
2009-07-19 12:47 ` Jean Delvare
2009-07-19 12:52 ` Mark Lord
2009-07-19 12:55 ` Jean Delvare
2009-07-19 13:10 ` Mark Lord
2009-07-19 13:17 ` Mark Lord
2009-07-19 14:38 ` Mark Lord
2009-07-19 17:08 ` Jean Delvare
2009-07-19 18:15 ` Mark Lord
2009-07-19 18:26 ` Mark Lord
2009-07-19 19:20 ` Regression 2.6.31: ioctl(EVIOCGNAME) no longer returns device name Mark Lord
2009-07-19 19:39 ` Dmitry Torokhov
2009-07-19 20:14 ` Mark Lord
2009-07-20 11:21 ` Andy Walls
2009-07-19 19:40 ` Jean Delvare
2009-07-19 19:31 ` [PATCH 1/3] ir-kbd-i2c: Allow use of ir-kdb-i2c internal get_key funcs and set ir_type Dmitry Torokhov
2009-07-19 16:29 ` Jean Delvare
2009-07-21 0:07 ` Andy Walls
2009-07-21 9:14 ` Jean Delvare
2009-07-17 20:46 ` [PATCH 2/3] 2/3: cx18: Add i2c initialization for Z8F0811/Hauppage IR transceivers Andy Walls
2009-07-19 13:38 ` Jean Delvare
2009-07-20 18:51 ` Jarod Wilson
2009-07-20 23:40 ` Andy Walls
2009-07-21 0:26 ` Andy Walls
2009-07-17 20:49 ` [PATCH 3/3] ir-kbd-i2c: Add support " Andy Walls
2009-07-19 19:22 ` Jean Delvare [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=20090719212206.593f9eeb@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=awalls@radix.net \
--cc=hverkuil@xs4all.nl \
--cc=isely@pobox.com \
--cc=j@jannau.net \
--cc=jarod@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=lkml@rtr.ca \
--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