V4L/DVB: Break Remote Controller keymaps into modules
The original Remote Controller approach were very messy: a big file,
that were part of ir-common kernel module, containing 64 different
RC keymap tables, used by the V4L/DVB drivers.
Better to break each RC keymap table into a separate module,
registering them into rc core on a process similar to the fs/nls tables.
As an userspace program is now in charge of loading those tables,
adds an option to allow the complete removal of those tables from
kernelspace.
Yet, on embedded devices like Set Top Boxes and TV sets, maybe the
only available input device is the IR. So, we should keep allowing
the usage of in-kernel tables, but a latter patch should change
the default to 'n', after giving some time for distros to add
the v4l-utils with the ir-keytable program, to allow the table
load via userspace.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-04-02 13:05:46 +07:00
|
|
|
/* kaiomy.h - Keytable for kaiomy Remote Controller
|
|
|
|
|
*
|
|
|
|
|
* keymap imported from ir-keymaps.c
|
|
|
|
|
*
|
2014-02-07 17:03:07 +07:00
|
|
|
* Copyright (c) 2010 by Mauro Carvalho Chehab
|
V4L/DVB: Break Remote Controller keymaps into modules
The original Remote Controller approach were very messy: a big file,
that were part of ir-common kernel module, containing 64 different
RC keymap tables, used by the V4L/DVB drivers.
Better to break each RC keymap table into a separate module,
registering them into rc core on a process similar to the fs/nls tables.
As an userspace program is now in charge of loading those tables,
adds an option to allow the complete removal of those tables from
kernelspace.
Yet, on embedded devices like Set Top Boxes and TV sets, maybe the
only available input device is the IR. So, we should keep allowing
the usage of in-kernel tables, but a latter patch should change
the default to 'n', after giving some time for distros to add
the v4l-utils with the ir-keytable program, to allow the table
load via userspace.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-04-02 13:05:46 +07:00
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
|
* the Free Software Foundation; either version 2 of the License, or
|
|
|
|
|
* (at your option) any later version.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include <media/rc-map.h>
|
2011-07-04 01:03:12 +07:00
|
|
|
#include <linux/module.h>
|
V4L/DVB: Break Remote Controller keymaps into modules
The original Remote Controller approach were very messy: a big file,
that were part of ir-common kernel module, containing 64 different
RC keymap tables, used by the V4L/DVB drivers.
Better to break each RC keymap table into a separate module,
registering them into rc core on a process similar to the fs/nls tables.
As an userspace program is now in charge of loading those tables,
adds an option to allow the complete removal of those tables from
kernelspace.
Yet, on embedded devices like Set Top Boxes and TV sets, maybe the
only available input device is the IR. So, we should keep allowing
the usage of in-kernel tables, but a latter patch should change
the default to 'n', after giving some time for distros to add
the v4l-utils with the ir-keytable program, to allow the table
load via userspace.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-04-02 13:05:46 +07:00
|
|
|
|
|
|
|
|
/* Kaiomy TVnPC U2
|
|
|
|
|
Mauro Carvalho Chehab <mchehab@infradead.org>
|
|
|
|
|
*/
|
|
|
|
|
|
[media] rc: Name RC keymap tables as rc_map_table
Remote keytables had different names all over the place. Part of the fault
is due to a bad naming when rc subsystem was created, but there were lots
of old names that were still here.
Use a common standard for everything.
Patch generated by this script:
for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,ir_scancode,rc_map_table,g <$i >a && mv a $i; done
for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,ir_codes_,rc_map_,g <$i >a && mv a $i; done
for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,rc_key_map,rc_map_table,g <$i >a && mv a $i; done
for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,rc_map_table_size,rc_map_size,g <$i >a && mv a $i; done
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-11-18 01:46:09 +07:00
|
|
|
static struct rc_map_table kaiomy[] = {
|
V4L/DVB: Break Remote Controller keymaps into modules
The original Remote Controller approach were very messy: a big file,
that were part of ir-common kernel module, containing 64 different
RC keymap tables, used by the V4L/DVB drivers.
Better to break each RC keymap table into a separate module,
registering them into rc core on a process similar to the fs/nls tables.
As an userspace program is now in charge of loading those tables,
adds an option to allow the complete removal of those tables from
kernelspace.
Yet, on embedded devices like Set Top Boxes and TV sets, maybe the
only available input device is the IR. So, we should keep allowing
the usage of in-kernel tables, but a latter patch should change
the default to 'n', after giving some time for distros to add
the v4l-utils with the ir-keytable program, to allow the table
load via userspace.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-04-02 13:05:46 +07:00
|
|
|
{ 0x43, KEY_POWER2},
|
|
|
|
|
{ 0x01, KEY_LIST},
|
|
|
|
|
{ 0x0b, KEY_ZOOM},
|
|
|
|
|
{ 0x03, KEY_POWER},
|
|
|
|
|
|
|
|
|
|
{ 0x04, KEY_1},
|
|
|
|
|
{ 0x08, KEY_2},
|
|
|
|
|
{ 0x02, KEY_3},
|
|
|
|
|
|
|
|
|
|
{ 0x0f, KEY_4},
|
|
|
|
|
{ 0x05, KEY_5},
|
|
|
|
|
{ 0x06, KEY_6},
|
|
|
|
|
|
|
|
|
|
{ 0x0c, KEY_7},
|
|
|
|
|
{ 0x0d, KEY_8},
|
|
|
|
|
{ 0x0a, KEY_9},
|
|
|
|
|
|
|
|
|
|
{ 0x11, KEY_0},
|
|
|
|
|
|
|
|
|
|
{ 0x09, KEY_CHANNELUP},
|
|
|
|
|
{ 0x07, KEY_CHANNELDOWN},
|
|
|
|
|
|
|
|
|
|
{ 0x0e, KEY_VOLUMEUP},
|
|
|
|
|
{ 0x13, KEY_VOLUMEDOWN},
|
|
|
|
|
|
|
|
|
|
{ 0x10, KEY_HOME},
|
|
|
|
|
{ 0x12, KEY_ENTER},
|
|
|
|
|
|
|
|
|
|
{ 0x14, KEY_RECORD},
|
|
|
|
|
{ 0x15, KEY_STOP},
|
|
|
|
|
{ 0x16, KEY_PLAY},
|
|
|
|
|
{ 0x17, KEY_MUTE},
|
|
|
|
|
|
|
|
|
|
{ 0x18, KEY_UP},
|
|
|
|
|
{ 0x19, KEY_DOWN},
|
|
|
|
|
{ 0x1a, KEY_LEFT},
|
|
|
|
|
{ 0x1b, KEY_RIGHT},
|
|
|
|
|
|
|
|
|
|
{ 0x1c, KEY_RED},
|
|
|
|
|
{ 0x1d, KEY_GREEN},
|
|
|
|
|
{ 0x1e, KEY_YELLOW},
|
|
|
|
|
{ 0x1f, KEY_BLUE},
|
|
|
|
|
};
|
|
|
|
|
|
2010-11-18 01:56:53 +07:00
|
|
|
static struct rc_map_list kaiomy_map = {
|
V4L/DVB: Break Remote Controller keymaps into modules
The original Remote Controller approach were very messy: a big file,
that were part of ir-common kernel module, containing 64 different
RC keymap tables, used by the V4L/DVB drivers.
Better to break each RC keymap table into a separate module,
registering them into rc core on a process similar to the fs/nls tables.
As an userspace program is now in charge of loading those tables,
adds an option to allow the complete removal of those tables from
kernelspace.
Yet, on embedded devices like Set Top Boxes and TV sets, maybe the
only available input device is the IR. So, we should keep allowing
the usage of in-kernel tables, but a latter patch should change
the default to 'n', after giving some time for distros to add
the v4l-utils with the ir-keytable program, to allow the table
load via userspace.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-04-02 13:05:46 +07:00
|
|
|
.map = {
|
2017-08-08 03:20:58 +07:00
|
|
|
.scan = kaiomy,
|
|
|
|
|
.size = ARRAY_SIZE(kaiomy),
|
|
|
|
|
.rc_proto = RC_PROTO_UNKNOWN, /* Legacy IR type */
|
|
|
|
|
.name = RC_MAP_KAIOMY,
|
V4L/DVB: Break Remote Controller keymaps into modules
The original Remote Controller approach were very messy: a big file,
that were part of ir-common kernel module, containing 64 different
RC keymap tables, used by the V4L/DVB drivers.
Better to break each RC keymap table into a separate module,
registering them into rc core on a process similar to the fs/nls tables.
As an userspace program is now in charge of loading those tables,
adds an option to allow the complete removal of those tables from
kernelspace.
Yet, on embedded devices like Set Top Boxes and TV sets, maybe the
only available input device is the IR. So, we should keep allowing
the usage of in-kernel tables, but a latter patch should change
the default to 'n', after giving some time for distros to add
the v4l-utils with the ir-keytable program, to allow the table
load via userspace.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-04-02 13:05:46 +07:00
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static int __init init_rc_map_kaiomy(void)
|
|
|
|
|
{
|
2010-11-18 01:56:53 +07:00
|
|
|
return rc_map_register(&kaiomy_map);
|
V4L/DVB: Break Remote Controller keymaps into modules
The original Remote Controller approach were very messy: a big file,
that were part of ir-common kernel module, containing 64 different
RC keymap tables, used by the V4L/DVB drivers.
Better to break each RC keymap table into a separate module,
registering them into rc core on a process similar to the fs/nls tables.
As an userspace program is now in charge of loading those tables,
adds an option to allow the complete removal of those tables from
kernelspace.
Yet, on embedded devices like Set Top Boxes and TV sets, maybe the
only available input device is the IR. So, we should keep allowing
the usage of in-kernel tables, but a latter patch should change
the default to 'n', after giving some time for distros to add
the v4l-utils with the ir-keytable program, to allow the table
load via userspace.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-04-02 13:05:46 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void __exit exit_rc_map_kaiomy(void)
|
|
|
|
|
{
|
2010-11-18 01:56:53 +07:00
|
|
|
rc_map_unregister(&kaiomy_map);
|
V4L/DVB: Break Remote Controller keymaps into modules
The original Remote Controller approach were very messy: a big file,
that were part of ir-common kernel module, containing 64 different
RC keymap tables, used by the V4L/DVB drivers.
Better to break each RC keymap table into a separate module,
registering them into rc core on a process similar to the fs/nls tables.
As an userspace program is now in charge of loading those tables,
adds an option to allow the complete removal of those tables from
kernelspace.
Yet, on embedded devices like Set Top Boxes and TV sets, maybe the
only available input device is the IR. So, we should keep allowing
the usage of in-kernel tables, but a latter patch should change
the default to 'n', after giving some time for distros to add
the v4l-utils with the ir-keytable program, to allow the table
load via userspace.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-04-02 13:05:46 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
module_init(init_rc_map_kaiomy)
|
|
|
|
|
module_exit(exit_rc_map_kaiomy)
|
|
|
|
|
|
|
|
|
|
MODULE_LICENSE("GPL");
|
2014-02-07 17:03:07 +07:00
|
|
|
MODULE_AUTHOR("Mauro Carvalho Chehab");
|