2
0
mirror of https://github.com/edk2-porting/linux-next.git synced 2025-01-25 07:06:40 +08:00
linux-next/drivers/media/video/omap
Archit Taneja e144ca6426 [media] OMAP_VOUT: Fix VSYNC IRQ handling in omap_vout_isr
Currently, in omap_vout_isr(), if the panel type is DPI, and if we
get either VSYNC or VSYNC2 interrupts, we proceed ahead to set the
current buffers state to VIDEOBUF_DONE and prepare to display the
next frame in the queue.

On OMAP4, because we have 2 LCD managers, the panel type itself is not
sufficient to tell if we have received the correct irq, i.e, we shouldn't
proceed ahead if we get a VSYNC interrupt for LCD2 manager, or a VSYNC2
interrupt for LCD manager.

Fix this by correlating LCD manager to VSYNC interrupt and LCD2 manager
to VSYNC2 interrupt.

Signed-off-by: Archit Taneja <archit@ti.com>
Reviewed-by: Sumit Semwal <sumit.semwal@ti.com>
Acked-by: Vaibhav Hiremath <hvaibhav@ti.com>
Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-11-07 11:18:54 -02:00
..
Kconfig [media] OMAP_VOUT: Create separate file for VRFB related API's 2011-07-27 17:56:06 -03:00
Makefile [media] OMAP_VOUT: Create separate file for VRFB related API's 2011-07-27 17:56:06 -03:00
omap_vout_vrfb.c [media] OMAP_VOUT: Create separate file for VRFB related API's 2011-07-27 17:56:06 -03:00
omap_vout_vrfb.h [media] OMAP_VOUT: Create separate file for VRFB related API's 2011-07-27 17:56:06 -03:00
omap_vout.c [media] OMAP_VOUT: Fix VSYNC IRQ handling in omap_vout_isr 2011-11-07 11:18:54 -02:00
omap_voutdef.h [media] OMAP_VOUT: Create separate file for VRFB related API's 2011-07-27 17:56:06 -03:00
omap_voutlib.c [media] OMAP_VOUT: CLEANUP: Move generic functions and macros to common files 2011-07-27 17:56:05 -03:00
omap_voutlib.h [media] OMAP_VOUT: CLEANUP: Move generic functions and macros to common files 2011-07-27 17:56:05 -03:00