kernel/git/stable/linux-stable.git/drivers/media/rc, branch linux-3.12.y

ite-cir: initialize use_demodulator before using it

2017-01-27T10:15:58+00:00

commit 7ec03e60ef81c19b5d3a46dd070ee966774b860f upstream. Function ite_set_carrier_params() uses variable use_demodulator after having initialized it to false in some if branches, but this variable is never set to true otherwise. This bug has been found using clang -Wsometimes-uninitialized warning flag. Fixes: 620a32bba4a2 ("[media] rc: New rc-based ite-cir driver for several ITE CIRs") Signed-off-by: Nicolas Iooss Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Jiri Slaby

rc-core: fix remove uevent generation

2015-09-30T09:13:08+00:00

commit a66b0c41ad277ae62a3ae6ac430a71882f899557 upstream. The input_dev is already gone when the rc device is being unregistered so checking for its presence only means that no remove uevent will be generated. Signed-off-by: David Härdeman Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Jiri Slaby

[media] media/rc: Send sync space information on the lirc device

2015-02-13T11:05:12+00:00

commit a8f29e89f2b54fbf2c52be341f149bc195b63a8b upstream. Userspace expects to see a long space before the first pulse is sent on the lirc device. Currently, if a long time has passed and a new packet is started, the lirc codec just returns and doesn't send anything. This makes lircd ignore many perfectly valid signals unless they are sent in quick sucession. When a reset event is delivered, we cannot know anything about the duration of the space. But it should be safe to assume it has been a long time and we just set the duration to maximum. Signed-off-by: Austin Lund Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Jiri Slaby

[media] media: rc: rdev->open or rdev->close can be NULL

2013-08-23T08:41:23+00:00

At least technisat-usb2.c doesn't set these... Signed-off-by: Juergen Lock Signed-off-by: Mauro Carvalho Chehab

[media] winbond: wire up rc feedback led

2013-08-22T14:49:18+00:00

Note that with the rc-feedback trigger, the cir-rx trigger is now redundant. The cir-tx trigger is not used by default; if this functionality is desired then it should exist in rc-core, not in a driver. Also make sure that the led is suspended on suspend. Signed-off-by: Sean Young Signed-off-by: David Härdeman Signed-off-by: Mauro Carvalho Chehab

[media] ttusbir: wire up rc feedback led

2013-08-22T14:48:32+00:00

Signed-off-by: Sean Young Signed-off-by: Mauro Carvalho Chehab

[media] redrat3: wire up rc feedback led

2013-08-22T14:48:02+00:00

Signed-off-by: Sean Young Signed-off-by: Mauro Carvalho Chehab

[media] rc: add feedback led trigger for rc keypresses

2013-08-22T14:46:46+00:00

Many devices with an ir receiver also have a feedback led. Add the led trigger to support this. Signed-off-by: Sean Young Signed-off-by: Mauro Carvalho Chehab

[media] redrat3: ensure whole packet is read

2013-08-22T14:45:32+00:00

The length in the header excludes the header itself, so we're getting spurious readings. Signed-off-by: Sean Young Signed-off-by: Mauro Carvalho Chehab

[media] media: lirc: Allow lirc dev to talk to rc device

2013-07-31T19:30:27+00:00

The use case is simple, if any rc device has allowed protocols = RC_TYPE_LIRC and map_name = RC_MAP_LIRC set, the driver open will be never called. The reason for this is, all of the key maps except lirc have some KEYS in there map, so during rc_register_device process these keys are matched against the input drivers and open is performed, so for the case of RC_MAP_EMPTY, a vt/keyboard is matched and the driver open is performed. In case of lirc, there is no match and result is that there is no open performed, however the lirc-dev will go ahead and create a /dev/lirc0 node. Now when lircd/mode2 opens this device, no data is available because the driver was never opened. Other case pointed by Sean Young, As rc device gets opened via the input interface. If the input device is never opened (e.g. embedded with no console) then the rc open is never called and lirc will not work either. So that's another case. lirc_dev seems to have no link with actual rc device w.r.t open/close. This patch adds rc_dev pointer to lirc_driver structure for cases like this, so that it can do the open/close of the real driver in accordance to lircd/mode2 open/close. Without this patch its impossible to open a rc device which has RC_TYPE_LIRC ad RC_MAP_LIRC set. Signed-off-by: Srinivas Kandagatla Signed-off-by: Mauro Carvalho Chehab