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
..
Kconfig
Makefile
saa6752hs.c
saa7134-alsa.c
saa7134-cards.c	[media] tuner-core: remove usage of DIGITAL_TV	2011-03-21 20:32:03 -03:00
saa7134-core.c	[media] saa7134: Properly report when a board doesn't have eeprom	2011-03-21 20:31:48 -03:00
saa7134-dvb.c	[media] saa7134: Kworld SBTVD: make both analog and digital to work	2011-01-19 11:45:28 -02:00
saa7134-empress.c	[media] saa7134-empress: add missing MPEG controls	2011-03-21 20:32:12 -03:00
saa7134-i2c.c
saa7134-input.c	[media] saa7134-input: key up events not sent after suspend/resume	2011-03-22 16:37:53 -03:00
saa7134-reg.h
saa7134-ts.c
saa7134-tvaudio.c
saa7134-vbi.c
saa7134-video.c	[media] v4l: fix handling of v4l2_input.capabilities	2010-12-30 08:02:29 -02:00
saa7134.h	[media] add support for Encore FM3	2011-03-21 20:31:49 -03:00