2017-12-01 13:47:11 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0+
|
|
|
|
// behold.h - Keytable for behold Remote Controller
|
|
|
|
//
|
|
|
|
// keymap imported from ir-keymaps.c
|
|
|
|
//
|
|
|
|
// 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 06:05:46 +00:00
|
|
|
|
|
|
|
#include <media/rc-map.h>
|
2011-07-03 18:03:12 +00: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 06:05:46 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Igor Kuznetsov <igk72@ya.ru>
|
|
|
|
* Andrey J. Melnikov <temnota@kmv.ru>
|
|
|
|
*
|
|
|
|
* Keytable is used by BeholdTV 60x series, M6 series at
|
|
|
|
* least, and probably other cards too.
|
|
|
|
* The "ascii-art picture" below (in comments, first row
|
|
|
|
* is the keycode in hex, and subsequent row(s) shows
|
|
|
|
* the button labels (several variants when appropriate)
|
|
|
|
* helps to descide which keycodes to assign to the buttons.
|
|
|
|
*/
|
|
|
|
|
[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-17 18:46:09 +00:00
|
|
|
static struct rc_map_table behold[] = {
|
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 06:05:46 +00:00
|
|
|
|
|
|
|
/* 0x1c 0x12 *
|
|
|
|
* TV/FM POWER *
|
|
|
|
* */
|
2014-04-03 23:32:01 +00:00
|
|
|
{ 0x866b1c, KEY_TUNER }, /* XXX KEY_TV / KEY_RADIO */
|
|
|
|
{ 0x866b12, KEY_POWER },
|
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 06:05:46 +00:00
|
|
|
|
|
|
|
/* 0x01 0x02 0x03 *
|
|
|
|
* 1 2 3 *
|
|
|
|
* *
|
|
|
|
* 0x04 0x05 0x06 *
|
|
|
|
* 4 5 6 *
|
|
|
|
* *
|
|
|
|
* 0x07 0x08 0x09 *
|
|
|
|
* 7 8 9 *
|
|
|
|
* */
|
2014-04-03 23:32:01 +00:00
|
|
|
{ 0x866b01, KEY_1 },
|
|
|
|
{ 0x866b02, KEY_2 },
|
|
|
|
{ 0x866b03, KEY_3 },
|
|
|
|
{ 0x866b04, KEY_4 },
|
|
|
|
{ 0x866b05, KEY_5 },
|
|
|
|
{ 0x866b06, KEY_6 },
|
|
|
|
{ 0x866b07, KEY_7 },
|
|
|
|
{ 0x866b08, KEY_8 },
|
|
|
|
{ 0x866b09, KEY_9 },
|
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 06:05:46 +00:00
|
|
|
|
|
|
|
/* 0x0a 0x00 0x17 *
|
|
|
|
* RECALL 0 MODE *
|
|
|
|
* */
|
2014-04-03 23:32:01 +00:00
|
|
|
{ 0x866b0a, KEY_AGAIN },
|
|
|
|
{ 0x866b00, KEY_0 },
|
|
|
|
{ 0x866b17, KEY_MODE },
|
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 06:05:46 +00:00
|
|
|
|
|
|
|
/* 0x14 0x10 *
|
|
|
|
* ASPECT FULLSCREEN *
|
|
|
|
* */
|
2014-04-03 23:32:01 +00:00
|
|
|
{ 0x866b14, KEY_SCREEN },
|
|
|
|
{ 0x866b10, KEY_ZOOM },
|
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 06:05:46 +00:00
|
|
|
|
|
|
|
/* 0x0b *
|
|
|
|
* Up *
|
|
|
|
* *
|
|
|
|
* 0x18 0x16 0x0c *
|
|
|
|
* Left Ok Right *
|
|
|
|
* *
|
|
|
|
* 0x015 *
|
|
|
|
* Down *
|
|
|
|
* */
|
2014-04-03 23:32:01 +00:00
|
|
|
{ 0x866b0b, KEY_CHANNELUP },
|
|
|
|
{ 0x866b18, KEY_VOLUMEDOWN },
|
|
|
|
{ 0x866b16, KEY_OK }, /* XXX KEY_ENTER */
|
|
|
|
{ 0x866b0c, KEY_VOLUMEUP },
|
|
|
|
{ 0x866b15, KEY_CHANNELDOWN },
|
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 06:05:46 +00:00
|
|
|
|
|
|
|
/* 0x11 0x0d *
|
|
|
|
* MUTE INFO *
|
|
|
|
* */
|
2014-04-03 23:32:01 +00:00
|
|
|
{ 0x866b11, KEY_MUTE },
|
|
|
|
{ 0x866b0d, KEY_INFO },
|
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 06:05:46 +00:00
|
|
|
|
|
|
|
/* 0x0f 0x1b 0x1a *
|
|
|
|
* RECORD PLAY/PAUSE STOP *
|
|
|
|
* *
|
|
|
|
* 0x0e 0x1f 0x1e *
|
|
|
|
*TELETEXT AUDIO SOURCE *
|
|
|
|
* RED YELLOW *
|
|
|
|
* */
|
2014-04-03 23:32:01 +00:00
|
|
|
{ 0x866b0f, KEY_RECORD },
|
|
|
|
{ 0x866b1b, KEY_PLAYPAUSE },
|
|
|
|
{ 0x866b1a, KEY_STOP },
|
|
|
|
{ 0x866b0e, KEY_TEXT },
|
|
|
|
{ 0x866b1f, KEY_RED }, /*XXX KEY_AUDIO */
|
|
|
|
{ 0x866b1e, KEY_VIDEO },
|
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 06:05:46 +00:00
|
|
|
|
|
|
|
/* 0x1d 0x13 0x19 *
|
|
|
|
* SLEEP PREVIEW DVB *
|
|
|
|
* GREEN BLUE *
|
|
|
|
* */
|
2014-04-03 23:32:01 +00:00
|
|
|
{ 0x866b1d, KEY_SLEEP },
|
|
|
|
{ 0x866b13, KEY_GREEN },
|
|
|
|
{ 0x866b19, KEY_BLUE }, /* XXX KEY_SAT */
|
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 06:05:46 +00:00
|
|
|
|
|
|
|
/* 0x58 0x5c *
|
|
|
|
* FREEZE SNAPSHOT *
|
|
|
|
* */
|
2014-04-03 23:32:01 +00:00
|
|
|
{ 0x866b58, KEY_SLOW },
|
|
|
|
{ 0x866b5c, KEY_CAMERA },
|
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 06:05:46 +00:00
|
|
|
|
|
|
|
};
|
|
|
|
|
2010-11-17 18:56:53 +00:00
|
|
|
static struct rc_map_list behold_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 06:05:46 +00:00
|
|
|
.map = {
|
2017-08-07 20:20:58 +00:00
|
|
|
.scan = behold,
|
|
|
|
.size = ARRAY_SIZE(behold),
|
|
|
|
.rc_proto = RC_PROTO_NEC,
|
|
|
|
.name = RC_MAP_BEHOLD,
|
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 06:05:46 +00:00
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
static int __init init_rc_map_behold(void)
|
|
|
|
{
|
2010-11-17 18:56:53 +00:00
|
|
|
return rc_map_register(&behold_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 06:05:46 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static void __exit exit_rc_map_behold(void)
|
|
|
|
{
|
2010-11-17 18:56:53 +00:00
|
|
|
rc_map_unregister(&behold_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 06:05:46 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
module_init(init_rc_map_behold)
|
|
|
|
module_exit(exit_rc_map_behold)
|
|
|
|
|
|
|
|
MODULE_LICENSE("GPL");
|
2014-02-07 10:03:07 +00:00
|
|
|
MODULE_AUTHOR("Mauro Carvalho Chehab");
|