linux.git/drivers/media/rc, branch v3.12

[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

[media] media: rc: Add rc_open/close and use count to rc_dev

2013-07-31T19:28:01+00:00

This patch adds user count to rc_dev structure, the reason to add this
new member is to allow other code like lirc to open rc device directly.
In the existing code, rc device is only opened by input subsystem which
works ok if we have any input drivers to match. But in case like lirc
where there will be no input driver, rc device will be never opened.
Having this user count variable will be usefull to allow rc device to be
opened from code other than rc-main.
This patch also adds rc_open and rc_close functions for other drivers
like lirc to open and close rc devices. This functions safely increment
and decrement the user count. Other driver wanting to open rc device
should call rc_open and rc_close, rather than directly modifying the
rc_dev structure.

Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Mauro Carvalho Chehab

[media] lirc: make transmit interface consistent

2013-07-30T20:04:23+00:00

All lirc drivers that can transmit, return EINVAL when they are passed
more than IR data than they can send. That is, except for two drivers
which I touched.

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

[media] lirc: validate transmission ir data

2013-07-30T20:03:16+00:00

The lirc interface allows 255 u32 spaces and pulses, which are usec. If
the driver can handle this (e.g. winbond-cir) you can produce hours of
meaningless IR data and there is no method of interrupting it.

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