diff options
| author | Sean Young <sean@mess.org> | 2019-06-04 07:19:30 -0400 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab+samsung@kernel.org> | 2019-06-10 15:03:33 -0400 |
| commit | 71f49a8bf5c592413edb5c8839ec0e6d754db3e1 (patch) | |
| tree | 3a3e0c3dfb70a8adb411850edb5a4ce9108e1e26 /drivers/media/rc | |
| parent | eb5005df886b3989dde5378064cc23315f769290 (diff) | |
| download | linux-71f49a8bf5c592413edb5c8839ec0e6d754db3e1.tar.bz2 | |
media: ttpci: use rc-core for the IR receiver
The IR protocol can now only be set via the rc protocols sysfs file rather
than via module parameters or a custom procfs file. So, it is no longer
necessary to periodically check for protocol changes.
The IR_RCMM protocol does not decode the Philips RC-MM protocol (12, 24 or
32 bit variants) or any protocol rc-core can encode, so this is marked
RC_PROTO_UNKNOWN.
Tested on Technotrend/Hauppauge WinTV Nexus-S rev2.1, which comes
with a small black hauppauge remote.
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Diffstat (limited to 'drivers/media/rc')
| -rw-r--r-- | drivers/media/rc/keymaps/rc-hauppauge.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/media/rc/keymaps/rc-hauppauge.c b/drivers/media/rc/keymaps/rc-hauppauge.c index 582aa9012443..c117e9fc2697 100644 --- a/drivers/media/rc/keymaps/rc-hauppauge.c +++ b/drivers/media/rc/keymaps/rc-hauppauge.c @@ -233,6 +233,7 @@ static struct rc_map_table rc5_hauppauge_new[] = { * This one also uses RC-5 protocol * Keycodes start with address = 0x00 */ + { 0x000f, KEY_TV }, { 0x001f, KEY_TV }, { 0x0020, KEY_CHANNELUP }, { 0x000c, KEY_RADIO }, |