summaryrefslogtreecommitdiff
path: root/Documentation/video4linux/omap3isp.txt
diff options
context:
space:
mode:
authorSakari Ailus <sakari.ailus@iki.fi>2011-06-15 22:58:48 +0400
committerMauro Carvalho Chehab <mchehab@redhat.com>2011-08-29 19:38:51 +0400
commit69d232ae8e95a229e7544989d6014e875deeb121 (patch)
tree62cf4402ced27602fc1c7d2be90d6b8d4d4aa3aa /Documentation/video4linux/omap3isp.txt
parenteab00a0da292fa7118aaf20da78e834866de00ae (diff)
downloadlinux-69d232ae8e95a229e7544989d6014e875deeb121.tar.xz
[media] omap3isp: ccdc: Use generic frame sync event instead of private HS_VS event
The ccdc block in the omap3isp produces events whenever it starts receiving a new frame. A private HS_VS event was used for this previously. Now, the generic V4L2_EVENT_FRAME_SYNC event is being used for the purpose. This patch also provides the frame sequence number to user space. Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'Documentation/video4linux/omap3isp.txt')
-rw-r--r--Documentation/video4linux/omap3isp.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/Documentation/video4linux/omap3isp.txt b/Documentation/video4linux/omap3isp.txt
index 69be2c782b98..5dd1439b61fd 100644
--- a/Documentation/video4linux/omap3isp.txt
+++ b/Documentation/video4linux/omap3isp.txt
@@ -70,10 +70,11 @@ Events
The OMAP 3 ISP driver does support the V4L2 event interface on CCDC and
statistics (AEWB, AF and histogram) subdevs.
-The CCDC subdev produces V4L2_EVENT_OMAP3ISP_HS_VS type event on HS_VS
-interrupt which is used to signal frame start. The event is triggered exactly
-when the reception of the first line of the frame starts in the CCDC module.
-The event can be subscribed on the CCDC subdev.
+The CCDC subdev produces V4L2_EVENT_FRAME_SYNC type event on HS_VS
+interrupt which is used to signal frame start. Earlier version of this
+driver used V4L2_EVENT_OMAP3ISP_HS_VS for this purpose. The event is
+triggered exactly when the reception of the first line of the frame starts
+in the CCDC module. The event can be subscribed on the CCDC subdev.
(When using parallel interface one must pay account to correct configuration
of the VS signal polarity. This is automatically correct when using the serial