diff options
author | Mauro Carvalho Chehab <mchehab@redhat.com> | 2010-12-30 06:01:01 -0500 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2010-12-30 09:17:05 -0500 |
commit | b22374544b981b82f7319a02e6b718fc796e9cfa (patch) | |
tree | 5c44fb2984127c160c6be4ff81539ecc8c936602 /drivers/media/video | |
parent | 61ea3aa5bf309333c6655ccef825b4a765bff219 (diff) |
[media] bttv-input: Add a note about PV951 RC
When comparing lirc-i2c and ir-kbd-i2c/bttv-input logic, a difference
was noticed. As lirc-i2c will be removed soon, store the difference on
a comment inside ir-kbd-i2c, in order to preserve the knowledge we
have about that remote controller.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/media/video')
-rw-r--r-- | drivers/media/video/bt8xx/bttv-input.c | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/drivers/media/video/bt8xx/bttv-input.c b/drivers/media/video/bt8xx/bttv-input.c index 7f48306133be..97793b960600 100644 --- a/drivers/media/video/bt8xx/bttv-input.c +++ b/drivers/media/video/bt8xx/bttv-input.c | |||
@@ -354,6 +354,18 @@ static int get_key_pv951(struct IR_i2c *ir, u32 *ir_key, u32 *ir_raw) | |||
354 | return 0; | 354 | return 0; |
355 | dprintk(KERN_INFO DEVNAME ": key %02x\n", b); | 355 | dprintk(KERN_INFO DEVNAME ": key %02x\n", b); |
356 | 356 | ||
357 | /* | ||
358 | * NOTE: | ||
359 | * lirc_i2c maps the pv951 code as: | ||
360 | * addr = 0x61D6 | ||
361 | * cmd = bit_reverse (b) | ||
362 | * So, it seems that this device uses NEC extended | ||
363 | * I decided to not fix the table, due to two reasons: | ||
364 | * 1) Without the actual device, this is only a guess; | ||
365 | * 2) As the addr is not reported via I2C, nor can be changed, | ||
366 | * the device is bound to the vendor-provided RC. | ||
367 | */ | ||
368 | |||
357 | *ir_key = b; | 369 | *ir_key = b; |
358 | *ir_raw = b; | 370 | *ir_raw = b; |
359 | return 1; | 371 | return 1; |