summaryrefslogtreecommitdiffstats
path: root/Documentation/ABI
diff options
context:
space:
mode:
authorJames Hogan <james.hogan@imgtec.com>2014-01-16 19:56:22 -0300
committerMauro Carvalho Chehab <m.chehab@samsung.com>2014-02-04 13:09:00 -0200
commit70a2f9120ffdb9bf9732c55c3350cb002a78841d (patch)
treee81d3d52f20e338e6b485c35faf126a552a61e0b /Documentation/ABI
parentdef62216041a63d45d0fd0ff014abdc9832ee611 (diff)
downloadlinux-stable-70a2f9120ffdb9bf9732c55c3350cb002a78841d.tar.gz
linux-stable-70a2f9120ffdb9bf9732c55c3350cb002a78841d.tar.bz2
linux-stable-70a2f9120ffdb9bf9732c55c3350cb002a78841d.zip
[media] media: rc: only turn on LED if keypress generated
Since v3.12, specifically 153a60bb0fac ([media] rc: add feedback led trigger for rc keypresses), an LED trigger is activated on IR keydown whether or not a keypress is generated (i.e. even if there's no matching keycode). However the repeat and keyup logic isn't used unless there is a keypress, which results in non-keypress keydown events turning on the LED and not turning it off again. On the assumption that the intent was for the LED only to light up on valid key presses (you probably don't want it lighting up for the wrong remote control for example), move the led_trigger_event() call inside the keycode check. Signed-off-by: James Hogan <james.hogan@imgtec.com> Acked-by: Sean Young <sean@mess.org> Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
Diffstat (limited to 'Documentation/ABI')
0 files changed, 0 insertions, 0 deletions