2005-06-23 22:02:35 -07:00
|
|
|
/* dvb-usb-remote.c is part of the DVB USB library.
|
|
|
|
*
|
2006-09-30 02:53:48 -07:00
|
|
|
* Copyright (C) 2004-6 Patrick Boettcher (patrick.boettcher@desy.de)
|
2005-06-23 22:02:35 -07:00
|
|
|
* see dvb-usb-init.c for copyright information.
|
|
|
|
*
|
2007-05-08 23:57:56 -07:00
|
|
|
* This file contains functions for initializing the input-device and for handling remote-control-queries.
|
2005-06-23 22:02:35 -07:00
|
|
|
*/
|
|
|
|
#include "dvb-usb-common.h"
|
2006-08-27 19:01:24 -07:00
|
|
|
#include <linux/usb/input.h>
|
2005-06-23 22:02:35 -07:00
|
|
|
|
V4L/DVB (12599): dvb-usb-remote: Allow dynamically replacing the IR keycodes
Implements handler for EVIOCGKEYCODE/EVIOCSKEYCODE via adding two new callbacks
to the input device.
Since on dvb-usb a scan code has 16 bits, to fulfill rc5 standard codes, the default
getkeycode/setkeycode input methods would require the driver to spend up to 64 Kb of
a sparse table. Instead, add two new callbacks to the event device.
With this, it is now possible to replace the keycode tables. There are, however, a few
implementation details at the current patch:
1) It will replace the existing device keytable, instead of creating an instance
of the data. This works. However, if two devices pointing to the same table
were connected, changing the IR table of one will also change the IR table for
the other (the solution for this one is simple: just kmalloc some memory);
2) In order to change the scan code, you need first to change the key to
KEY_RESERVED or KEY_UNKNOWN to free some space at the table (solution: allocate
some additional space for newer scan codes or allow dynamic table grow);
3) The table size cannot be extended. It would be easy to allow the table to
grow dynamically: just calling kmalloc(size+1); kfree(old). Yet, maybe we can
just create a bigger table with a fixed size, like for example a table with 128
entries. This should be enough even for a very big IR.
The current issues should be addressed on a later patch.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2009-08-29 11:27:29 -07:00
|
|
|
static int dvb_usb_getkeycode(struct input_dev *dev,
|
2010-03-08 23:37:10 -07:00
|
|
|
unsigned int scancode, unsigned int *keycode)
|
V4L/DVB (12599): dvb-usb-remote: Allow dynamically replacing the IR keycodes
Implements handler for EVIOCGKEYCODE/EVIOCSKEYCODE via adding two new callbacks
to the input device.
Since on dvb-usb a scan code has 16 bits, to fulfill rc5 standard codes, the default
getkeycode/setkeycode input methods would require the driver to spend up to 64 Kb of
a sparse table. Instead, add two new callbacks to the event device.
With this, it is now possible to replace the keycode tables. There are, however, a few
implementation details at the current patch:
1) It will replace the existing device keytable, instead of creating an instance
of the data. This works. However, if two devices pointing to the same table
were connected, changing the IR table of one will also change the IR table for
the other (the solution for this one is simple: just kmalloc some memory);
2) In order to change the scan code, you need first to change the key to
KEY_RESERVED or KEY_UNKNOWN to free some space at the table (solution: allocate
some additional space for newer scan codes or allow dynamic table grow);
3) The table size cannot be extended. It would be easy to allow the table to
grow dynamically: just calling kmalloc(size+1); kfree(old). Yet, maybe we can
just create a bigger table with a fixed size, like for example a table with 128
entries. This should be enough even for a very big IR.
The current issues should be addressed on a later patch.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2009-08-29 11:27:29 -07:00
|
|
|
{
|
|
|
|
struct dvb_usb_device *d = input_get_drvdata(dev);
|
|
|
|
|
|
|
|
struct dvb_usb_rc_key *keymap = d->props.rc_key_map;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
/* See if we can match the raw key code. */
|
|
|
|
for (i = 0; i < d->props.rc_key_map_size; i++)
|
|
|
|
if (keymap[i].scan == scancode) {
|
|
|
|
*keycode = keymap[i].event;
|
|
|
|
return 0;
|
|
|
|
}
|
2009-08-29 18:03:47 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* If is there extra space, returns KEY_RESERVED,
|
|
|
|
* otherwise, input core won't let dvb_usb_setkeycode
|
|
|
|
* to work
|
|
|
|
*/
|
|
|
|
for (i = 0; i < d->props.rc_key_map_size; i++)
|
|
|
|
if (keymap[i].event == KEY_RESERVED ||
|
|
|
|
keymap[i].event == KEY_UNKNOWN) {
|
|
|
|
*keycode = KEY_RESERVED;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
V4L/DVB (12599): dvb-usb-remote: Allow dynamically replacing the IR keycodes
Implements handler for EVIOCGKEYCODE/EVIOCSKEYCODE via adding two new callbacks
to the input device.
Since on dvb-usb a scan code has 16 bits, to fulfill rc5 standard codes, the default
getkeycode/setkeycode input methods would require the driver to spend up to 64 Kb of
a sparse table. Instead, add two new callbacks to the event device.
With this, it is now possible to replace the keycode tables. There are, however, a few
implementation details at the current patch:
1) It will replace the existing device keytable, instead of creating an instance
of the data. This works. However, if two devices pointing to the same table
were connected, changing the IR table of one will also change the IR table for
the other (the solution for this one is simple: just kmalloc some memory);
2) In order to change the scan code, you need first to change the key to
KEY_RESERVED or KEY_UNKNOWN to free some space at the table (solution: allocate
some additional space for newer scan codes or allow dynamic table grow);
3) The table size cannot be extended. It would be easy to allow the table to
grow dynamically: just calling kmalloc(size+1); kfree(old). Yet, maybe we can
just create a bigger table with a fixed size, like for example a table with 128
entries. This should be enough even for a very big IR.
The current issues should be addressed on a later patch.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2009-08-29 11:27:29 -07:00
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int dvb_usb_setkeycode(struct input_dev *dev,
|
2010-03-08 23:37:10 -07:00
|
|
|
unsigned int scancode, unsigned int keycode)
|
V4L/DVB (12599): dvb-usb-remote: Allow dynamically replacing the IR keycodes
Implements handler for EVIOCGKEYCODE/EVIOCSKEYCODE via adding two new callbacks
to the input device.
Since on dvb-usb a scan code has 16 bits, to fulfill rc5 standard codes, the default
getkeycode/setkeycode input methods would require the driver to spend up to 64 Kb of
a sparse table. Instead, add two new callbacks to the event device.
With this, it is now possible to replace the keycode tables. There are, however, a few
implementation details at the current patch:
1) It will replace the existing device keytable, instead of creating an instance
of the data. This works. However, if two devices pointing to the same table
were connected, changing the IR table of one will also change the IR table for
the other (the solution for this one is simple: just kmalloc some memory);
2) In order to change the scan code, you need first to change the key to
KEY_RESERVED or KEY_UNKNOWN to free some space at the table (solution: allocate
some additional space for newer scan codes or allow dynamic table grow);
3) The table size cannot be extended. It would be easy to allow the table to
grow dynamically: just calling kmalloc(size+1); kfree(old). Yet, maybe we can
just create a bigger table with a fixed size, like for example a table with 128
entries. This should be enough even for a very big IR.
The current issues should be addressed on a later patch.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2009-08-29 11:27:29 -07:00
|
|
|
{
|
|
|
|
struct dvb_usb_device *d = input_get_drvdata(dev);
|
|
|
|
|
|
|
|
struct dvb_usb_rc_key *keymap = d->props.rc_key_map;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
/* Search if it is replacing an existing keycode */
|
|
|
|
for (i = 0; i < d->props.rc_key_map_size; i++)
|
|
|
|
if (keymap[i].scan == scancode) {
|
|
|
|
keymap[i].event = keycode;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Search if is there a clean entry. If so, use it */
|
|
|
|
for (i = 0; i < d->props.rc_key_map_size; i++)
|
|
|
|
if (keymap[i].event == KEY_RESERVED ||
|
|
|
|
keymap[i].event == KEY_UNKNOWN) {
|
|
|
|
keymap[i].scan = scancode;
|
|
|
|
keymap[i].event = keycode;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* FIXME: Currently, it is not possible to increase the size of
|
|
|
|
* scancode table. For it to happen, one possibility
|
|
|
|
* would be to allocate a table with key_map_size + 1,
|
|
|
|
* copying data, appending the new key on it, and freeing
|
|
|
|
* the old one - or maybe just allocating some spare space
|
|
|
|
*/
|
|
|
|
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2005-06-23 22:02:35 -07:00
|
|
|
/* Remote-control poll function - called every dib->rc_query_interval ms to see
|
|
|
|
* whether the remote control has received anything.
|
|
|
|
*
|
|
|
|
* TODO: Fix the repeat rate of the input device.
|
|
|
|
*/
|
2006-11-22 07:57:56 -07:00
|
|
|
static void dvb_usb_read_remote_control(struct work_struct *work)
|
2005-06-23 22:02:35 -07:00
|
|
|
{
|
2006-11-22 07:57:56 -07:00
|
|
|
struct dvb_usb_device *d =
|
|
|
|
container_of(work, struct dvb_usb_device, rc_query_work.work);
|
2005-06-23 22:02:35 -07:00
|
|
|
u32 event;
|
|
|
|
int state;
|
|
|
|
|
|
|
|
/* TODO: need a lock here. We can simply skip checking for the remote control
|
|
|
|
if we're busy. */
|
|
|
|
|
2005-07-07 17:58:11 -07:00
|
|
|
/* when the parameter has been set to 1 via sysfs while the driver was running */
|
|
|
|
if (dvb_usb_disable_rc_polling)
|
|
|
|
return;
|
|
|
|
|
2005-06-23 22:02:35 -07:00
|
|
|
if (d->props.rc_query(d,&event,&state)) {
|
|
|
|
err("error while querying for an remote control event.");
|
|
|
|
goto schedule;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
switch (state) {
|
|
|
|
case REMOTE_NO_KEY_PRESSED:
|
|
|
|
break;
|
|
|
|
case REMOTE_KEY_PRESSED:
|
|
|
|
deb_rc("key pressed\n");
|
|
|
|
d->last_event = event;
|
|
|
|
case REMOTE_KEY_REPEAT:
|
|
|
|
deb_rc("key repeated\n");
|
2005-09-15 00:01:53 -07:00
|
|
|
input_event(d->rc_input_dev, EV_KEY, event, 1);
|
2010-02-14 13:36:25 -07:00
|
|
|
input_sync(d->rc_input_dev);
|
2005-09-15 00:01:53 -07:00
|
|
|
input_event(d->rc_input_dev, EV_KEY, d->last_event, 0);
|
|
|
|
input_sync(d->rc_input_dev);
|
2005-06-23 22:02:35 -07:00
|
|
|
break;
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* improved repeat handling ???
|
|
|
|
switch (state) {
|
|
|
|
case REMOTE_NO_KEY_PRESSED:
|
|
|
|
deb_rc("NO KEY PRESSED\n");
|
|
|
|
if (d->last_state != REMOTE_NO_KEY_PRESSED) {
|
|
|
|
deb_rc("releasing event %d\n",d->last_event);
|
2005-09-15 00:01:53 -07:00
|
|
|
input_event(d->rc_input_dev, EV_KEY, d->last_event, 0);
|
|
|
|
input_sync(d->rc_input_dev);
|
2005-06-23 22:02:35 -07:00
|
|
|
}
|
|
|
|
d->last_state = REMOTE_NO_KEY_PRESSED;
|
|
|
|
d->last_event = 0;
|
|
|
|
break;
|
|
|
|
case REMOTE_KEY_PRESSED:
|
|
|
|
deb_rc("KEY PRESSED\n");
|
|
|
|
deb_rc("pressing event %d\n",event);
|
|
|
|
|
2005-09-15 00:01:53 -07:00
|
|
|
input_event(d->rc_input_dev, EV_KEY, event, 1);
|
|
|
|
input_sync(d->rc_input_dev);
|
2005-06-23 22:02:35 -07:00
|
|
|
|
|
|
|
d->last_event = event;
|
|
|
|
d->last_state = REMOTE_KEY_PRESSED;
|
|
|
|
break;
|
|
|
|
case REMOTE_KEY_REPEAT:
|
|
|
|
deb_rc("KEY_REPEAT\n");
|
|
|
|
if (d->last_state != REMOTE_NO_KEY_PRESSED) {
|
|
|
|
deb_rc("repeating event %d\n",d->last_event);
|
2005-09-15 00:01:53 -07:00
|
|
|
input_event(d->rc_input_dev, EV_KEY, d->last_event, 2);
|
|
|
|
input_sync(d->rc_input_dev);
|
2005-06-23 22:02:35 -07:00
|
|
|
d->last_state = REMOTE_KEY_REPEAT;
|
|
|
|
}
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
*/
|
|
|
|
|
|
|
|
schedule:
|
|
|
|
schedule_delayed_work(&d->rc_query_work,msecs_to_jiffies(d->props.rc_interval));
|
|
|
|
}
|
|
|
|
|
|
|
|
int dvb_usb_remote_init(struct dvb_usb_device *d)
|
|
|
|
{
|
2006-11-20 06:23:04 -07:00
|
|
|
struct input_dev *input_dev;
|
2005-06-23 22:02:35 -07:00
|
|
|
int i;
|
2006-11-20 06:23:04 -07:00
|
|
|
int err;
|
2005-09-15 00:01:53 -07:00
|
|
|
|
2005-07-07 17:58:11 -07:00
|
|
|
if (d->props.rc_key_map == NULL ||
|
|
|
|
d->props.rc_query == NULL ||
|
|
|
|
dvb_usb_disable_rc_polling)
|
2005-06-23 22:02:35 -07:00
|
|
|
return 0;
|
|
|
|
|
2005-09-15 00:01:53 -07:00
|
|
|
usb_make_path(d->udev, d->rc_phys, sizeof(d->rc_phys));
|
2006-08-27 19:01:24 -07:00
|
|
|
strlcat(d->rc_phys, "/ir0", sizeof(d->rc_phys));
|
2005-09-15 00:01:53 -07:00
|
|
|
|
2006-11-20 06:23:04 -07:00
|
|
|
input_dev = input_allocate_device();
|
|
|
|
if (!input_dev)
|
2005-09-15 00:01:53 -07:00
|
|
|
return -ENOMEM;
|
2005-06-23 22:02:35 -07:00
|
|
|
|
2007-10-18 23:40:32 -07:00
|
|
|
input_dev->evbit[0] = BIT_MASK(EV_KEY);
|
2006-11-20 06:23:04 -07:00
|
|
|
input_dev->name = "IR-receiver inside an USB DVB receiver";
|
|
|
|
input_dev->phys = d->rc_phys;
|
|
|
|
usb_to_input_id(d->udev, &input_dev->id);
|
2007-07-16 05:28:15 -07:00
|
|
|
input_dev->dev.parent = &d->udev->dev;
|
V4L/DVB (12599): dvb-usb-remote: Allow dynamically replacing the IR keycodes
Implements handler for EVIOCGKEYCODE/EVIOCSKEYCODE via adding two new callbacks
to the input device.
Since on dvb-usb a scan code has 16 bits, to fulfill rc5 standard codes, the default
getkeycode/setkeycode input methods would require the driver to spend up to 64 Kb of
a sparse table. Instead, add two new callbacks to the event device.
With this, it is now possible to replace the keycode tables. There are, however, a few
implementation details at the current patch:
1) It will replace the existing device keytable, instead of creating an instance
of the data. This works. However, if two devices pointing to the same table
were connected, changing the IR table of one will also change the IR table for
the other (the solution for this one is simple: just kmalloc some memory);
2) In order to change the scan code, you need first to change the key to
KEY_RESERVED or KEY_UNKNOWN to free some space at the table (solution: allocate
some additional space for newer scan codes or allow dynamic table grow);
3) The table size cannot be extended. It would be easy to allow the table to
grow dynamically: just calling kmalloc(size+1); kfree(old). Yet, maybe we can
just create a bigger table with a fixed size, like for example a table with 128
entries. This should be enough even for a very big IR.
The current issues should be addressed on a later patch.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2009-08-29 11:27:29 -07:00
|
|
|
input_dev->getkeycode = dvb_usb_getkeycode;
|
|
|
|
input_dev->setkeycode = dvb_usb_setkeycode;
|
2005-06-23 22:02:35 -07:00
|
|
|
|
|
|
|
/* set the bits for the keys */
|
2005-09-15 00:01:53 -07:00
|
|
|
deb_rc("key map size: %d\n", d->props.rc_key_map_size);
|
2005-06-23 22:02:35 -07:00
|
|
|
for (i = 0; i < d->props.rc_key_map_size; i++) {
|
2006-11-20 06:23:04 -07:00
|
|
|
deb_rc("setting bit for event %d item %d\n",
|
|
|
|
d->props.rc_key_map[i].event, i);
|
|
|
|
set_bit(d->props.rc_key_map[i].event, input_dev->keybit);
|
2005-06-23 22:02:35 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Start the remote-control polling. */
|
|
|
|
if (d->props.rc_interval < 40)
|
|
|
|
d->props.rc_interval = 100; /* default */
|
|
|
|
|
|
|
|
/* setting these two values to non-zero, we have to manage key repeats */
|
2006-11-20 06:23:04 -07:00
|
|
|
input_dev->rep[REP_PERIOD] = d->props.rc_interval;
|
|
|
|
input_dev->rep[REP_DELAY] = d->props.rc_interval + 150;
|
2005-06-23 22:02:35 -07:00
|
|
|
|
V4L/DVB (12599): dvb-usb-remote: Allow dynamically replacing the IR keycodes
Implements handler for EVIOCGKEYCODE/EVIOCSKEYCODE via adding two new callbacks
to the input device.
Since on dvb-usb a scan code has 16 bits, to fulfill rc5 standard codes, the default
getkeycode/setkeycode input methods would require the driver to spend up to 64 Kb of
a sparse table. Instead, add two new callbacks to the event device.
With this, it is now possible to replace the keycode tables. There are, however, a few
implementation details at the current patch:
1) It will replace the existing device keytable, instead of creating an instance
of the data. This works. However, if two devices pointing to the same table
were connected, changing the IR table of one will also change the IR table for
the other (the solution for this one is simple: just kmalloc some memory);
2) In order to change the scan code, you need first to change the key to
KEY_RESERVED or KEY_UNKNOWN to free some space at the table (solution: allocate
some additional space for newer scan codes or allow dynamic table grow);
3) The table size cannot be extended. It would be easy to allow the table to
grow dynamically: just calling kmalloc(size+1); kfree(old). Yet, maybe we can
just create a bigger table with a fixed size, like for example a table with 128
entries. This should be enough even for a very big IR.
The current issues should be addressed on a later patch.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2009-08-29 11:27:29 -07:00
|
|
|
input_set_drvdata(input_dev, d);
|
|
|
|
|
2006-11-20 06:23:04 -07:00
|
|
|
err = input_register_device(input_dev);
|
|
|
|
if (err) {
|
|
|
|
input_free_device(input_dev);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
d->rc_input_dev = input_dev;
|
2005-06-23 22:02:35 -07:00
|
|
|
|
2006-11-22 07:57:56 -07:00
|
|
|
INIT_DELAYED_WORK(&d->rc_query_work, dvb_usb_read_remote_control);
|
2005-06-23 22:02:35 -07:00
|
|
|
|
2005-09-15 00:01:53 -07:00
|
|
|
info("schedule remote query interval to %d msecs.", d->props.rc_interval);
|
2005-06-23 22:02:35 -07:00
|
|
|
schedule_delayed_work(&d->rc_query_work,msecs_to_jiffies(d->props.rc_interval));
|
|
|
|
|
|
|
|
d->state |= DVB_USB_STATE_REMOTE;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int dvb_usb_remote_exit(struct dvb_usb_device *d)
|
|
|
|
{
|
|
|
|
if (d->state & DVB_USB_STATE_REMOTE) {
|
2007-02-06 16:29:07 -07:00
|
|
|
cancel_rearming_delayed_work(&d->rc_query_work);
|
2005-06-23 22:02:35 -07:00
|
|
|
flush_scheduled_work();
|
2005-09-15 00:01:53 -07:00
|
|
|
input_unregister_device(d->rc_input_dev);
|
2005-06-23 22:02:35 -07:00
|
|
|
}
|
|
|
|
d->state &= ~DVB_USB_STATE_REMOTE;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
#define DVB_USB_RC_NEC_EMPTY 0x00
|
|
|
|
#define DVB_USB_RC_NEC_KEY_PRESSED 0x01
|
|
|
|
#define DVB_USB_RC_NEC_KEY_REPEATED 0x02
|
|
|
|
int dvb_usb_nec_rc_key_to_event(struct dvb_usb_device *d,
|
|
|
|
u8 keybuf[5], u32 *event, int *state)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
struct dvb_usb_rc_key *keymap = d->props.rc_key_map;
|
|
|
|
*event = 0;
|
|
|
|
*state = REMOTE_NO_KEY_PRESSED;
|
|
|
|
switch (keybuf[0]) {
|
|
|
|
case DVB_USB_RC_NEC_EMPTY:
|
|
|
|
break;
|
|
|
|
case DVB_USB_RC_NEC_KEY_PRESSED:
|
|
|
|
if ((u8) ~keybuf[1] != keybuf[2] ||
|
|
|
|
(u8) ~keybuf[3] != keybuf[4]) {
|
|
|
|
deb_err("remote control checksum failed.\n");
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
/* See if we can match the raw key code. */
|
2005-07-07 17:58:24 -07:00
|
|
|
for (i = 0; i < d->props.rc_key_map_size; i++)
|
2009-08-29 11:19:31 -07:00
|
|
|
if (rc5_custom(&keymap[i]) == keybuf[1] &&
|
|
|
|
rc5_data(&keymap[i]) == keybuf[3]) {
|
2005-06-23 22:02:35 -07:00
|
|
|
*event = keymap[i].event;
|
|
|
|
*state = REMOTE_KEY_PRESSED;
|
2005-07-07 17:58:24 -07:00
|
|
|
return 0;
|
2005-06-23 22:02:35 -07:00
|
|
|
}
|
|
|
|
deb_err("key mapping failed - no appropriate key found in keymapping\n");
|
|
|
|
break;
|
|
|
|
case DVB_USB_RC_NEC_KEY_REPEATED:
|
|
|
|
*state = REMOTE_KEY_REPEAT;
|
|
|
|
break;
|
|
|
|
default:
|
tree-wide: fix assorted typos all over the place
That is "success", "unknown", "through", "performance", "[re|un]mapping"
, "access", "default", "reasonable", "[con]currently", "temperature"
, "channel", "[un]used", "application", "example","hierarchy", "therefore"
, "[over|under]flow", "contiguous", "threshold", "enough" and others.
Signed-off-by: André Goddard Rosa <andre.goddard@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
2009-11-14 08:09:05 -07:00
|
|
|
deb_err("unknown type of remote status: %d\n",keybuf[0]);
|
2005-06-23 22:02:35 -07:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(dvb_usb_nec_rc_key_to_event);
|