aboutsummaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorVadim Solomin <vadic052@gmail.com>2011-03-06 11:00:38 -0500
committerMauro Carvalho Chehab <mchehab@redhat.com>2011-03-22 15:37:53 -0400
commit8c1476ffc0b820f6ca8cc0b3f50c8a0f57e8d82d (patch)
treedce8b4f36f6f4424b6fcd55ee37ed3b135a01f63 /include
parentbc4b18c6f536de3733e247b07adcc9ea3f5684dd (diff)
[media] saa7134-input: key up events not sent after suspend/resume
On my AverMedia AverTV Studio 507, key up events are no longer sent after a suspend-to-disk/resume cycle, resulting in "stuck" keys. Apparently, for key up events to be generated, a certain GPIO pin must be set. Currently it's set in saa7134_input_init1(), but that function is not called on device resume. I suggest that code be moved to __saa7134_ir_start(), which is called both on init and resume. Signed-off-by: Vadim Solomin <vadic052@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions