V4L/DVB (9016): HVR3000/4000 Hauppauge related IR cleanups

From the author:
This patch-set fixes remote control issues I have experienced
with hauppauge drivers in Linux since the PVR-350 and now
with both a NOVA-S+ and HVR-4000. It has also been confirmed
to work with an HVR-1300 user who had exactly the same issue.

Hauppage remote controls use RC5. RC5 has a bit-field which
represents the target device. The hauppauge windows drivers
have a registry key which can enable filtering, but the linux
drivers will accept any target device in this bit field for
internal processing.

This causes problems with setups such as mythtv where remote
control key presses destined for the TV (target = 0) are
interpreted by the kernel and subsequenctly LIRC then mythtv.

Of the remote controls I have to hand (wintv black, pvr/hvr
silver) the hauppauge remotes send one of two device targets
ids, these are interpreted by the patch which then filters
out any non hauppauge addresses.

Signed-off-by: Steven Toth <stoth@linuxtv.org>
Signed-off-by: Darron Broad <darron@kewl.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

1 files changed, 20 insertions, 2 deletions

diff --git a/drivers/media/video/ir-kbd-i2c.c b/drivers/media/video/ir-kbd-i2c.c
index a30254bed311..703195a5ad4e 100644
--- a/drivers/media/video/ir-kbd-i2c.c
+++ b/drivers/media/video/ir-kbd-i2c.c
@@ -65,7 +65,7 @@ static int get_key_haup_common(struct IR_i2c *ir, u32 *ir_key, u32 *ir_raw,
                                int size, int offset)
 {
         unsigned char buf[6];
-        int start, range, toggle, dev, code;
+        int start, range, toggle, dev, code, ircode;
 
         /* poll IR chip */
         if (size != i2c_master_recv(&ir->c,buf,size))
@@ -85,6 +85,24 @@ static int get_key_haup_common(struct IR_i2c *ir, u32 *ir_key, u32 *ir_raw,
         if (!start)
                 /* no key pressed */
                 return 0;
+        /*
+         * Hauppauge remotes (black/silver) always use
+         * specific device ids. If we do not filter the
+         * device ids then messages destined for devices
+         * such as TVs (id=0) will get through causing
+         * mis-fired events.
+         *
+         * We also filter out invalid key presses which
+         * produce annoying debug log entries.
+         */
+        ircode= (start << 12) | (toggle << 11) | (dev << 6) | code;
+        if ((ircode & 0x1fff)==0x1fff)
+                /* invalid key press */
+                return 0;
+
+        if (dev!=0x1e && dev!=0x1f)
+                /* not a hauppauge remote */
+                return 0;
 
         if (!range)
                 code += 64;
@@ -94,7 +112,7 @@ static int get_key_haup_common(struct IR_i2c *ir, u32 *ir_key, u32 *ir_raw,
 
         /* return key */
         *ir_key = code;
-        *ir_raw = (start << 12) | (toggle << 11) | (dev << 6) | code;
+        *ir_raw = ircode;
         return 1;
 }