Commit 433763fa authored by Franklin Meng's avatar Franklin Meng Committed by Mauro Carvalho Chehab

V4L/DVB: Kworld 315U remote support

Adds remote support for the Kworld 315U device

I have added the change for the IR_TYPE_NEC that Mauro suggested.

Note: I believe I got most of the mappings correct.  Though the
source and shutdown button probably could be mapped to something
better.

[mchehab@redhat.com: Fix CodingStyle]
Signed-off-by: default avatarFranklin Meng <fmeng2002@yahoo.com>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
parent 96dd6de3
...@@ -3441,3 +3441,54 @@ struct ir_scancode_table ir_codes_winfast_usbii_deluxe_table = { ...@@ -3441,3 +3441,54 @@ struct ir_scancode_table ir_codes_winfast_usbii_deluxe_table = {
.size = ARRAY_SIZE(ir_codes_winfast_usbii_deluxe), .size = ARRAY_SIZE(ir_codes_winfast_usbii_deluxe),
}; };
EXPORT_SYMBOL_GPL(ir_codes_winfast_usbii_deluxe_table); EXPORT_SYMBOL_GPL(ir_codes_winfast_usbii_deluxe_table);
/* Kworld 315U
*/
static struct ir_scancode ir_codes_kworld_315u[] = {
{ 0x6143, KEY_POWER },
{ 0x6101, KEY_TUNER }, /* source */
{ 0x610b, KEY_ZOOM },
{ 0x6103, KEY_POWER2 }, /* shutdown */
{ 0x6104, KEY_1 },
{ 0x6108, KEY_2 },
{ 0x6102, KEY_3 },
{ 0x6109, KEY_CHANNELUP },
{ 0x610f, KEY_4 },
{ 0x6105, KEY_5 },
{ 0x6106, KEY_6 },
{ 0x6107, KEY_CHANNELDOWN },
{ 0x610c, KEY_7 },
{ 0x610d, KEY_8 },
{ 0x610a, KEY_9 },
{ 0x610e, KEY_VOLUMEUP },
{ 0x6110, KEY_LAST },
{ 0x6111, KEY_0 },
{ 0x6112, KEY_ENTER },
{ 0x6113, KEY_VOLUMEDOWN },
{ 0x6114, KEY_RECORD },
{ 0x6115, KEY_STOP },
{ 0x6116, KEY_PLAY },
{ 0x6117, KEY_MUTE },
{ 0x6118, KEY_UP },
{ 0x6119, KEY_DOWN },
{ 0x611a, KEY_LEFT },
{ 0x611b, KEY_RIGHT },
{ 0x611c, KEY_RED },
{ 0x611d, KEY_GREEN },
{ 0x611e, KEY_YELLOW },
{ 0x611f, KEY_BLUE },
};
struct ir_scancode_table ir_codes_kworld_315u_table = {
.scan = ir_codes_kworld_315u,
.size = ARRAY_SIZE(ir_codes_kworld_315u),
.ir_type = IR_TYPE_NEC,
};
EXPORT_SYMBOL_GPL(ir_codes_kworld_315u_table);
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment