linux/drivers/media
Vadim Solomin 8c1476ffc0 [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>
2011-03-22 16:37:53 -03:00
..
common [media] tuner-xc2028.c: fix compile warning 2011-03-22 04:53:58 -03:00
dvb [media] stv0367: typo in function parameter 2011-03-22 16:37:51 -03:00
radio [media] radio-wl1273: remove unused wl1273_device->work 2011-03-22 06:51:56 -03:00
rc [media] Change to 32 bit and add other remote controls for lme2510 2011-03-22 16:37:48 -03:00
video [media] saa7134-input: key up events not sent after suspend/resume 2011-03-22 16:37:53 -03:00
Kconfig [media] v4l: Create v4l2 subdev file handle structure 2011-03-22 04:53:26 -03:00
Makefile [media] media: Entities, pads and links 2011-03-22 04:53:10 -03:00
media-device.c [media] media: Links setup 2011-03-22 04:53:16 -03:00
media-devnode.c [media] media: Media device node support 2011-03-22 04:52:22 -03:00
media-entity.c [media] media: Pipelines and media streams 2011-03-22 04:53:17 -03:00