summaryrefslogtreecommitdiffstats
path: root/Documentation/video4linux
diff options
context:
space:
mode:
authorHans Verkuil <hverkuil@xs4all.nl>2015-06-01 07:15:53 -0300
committerMauro Carvalho Chehab <mchehab@osg.samsung.com>2015-06-06 07:33:17 -0300
commit63344b6592f1d69e13d0e32d8b213137ab6b663e (patch)
treeaa29b7423cf9b858acb77ca565e20ebd8e727f7b /Documentation/video4linux
parentcc1821964d122c39a80e653163513f11ccc39524 (diff)
downloadop-kernel-dev-63344b6592f1d69e13d0e32d8b213137ab6b663e.zip
op-kernel-dev-63344b6592f1d69e13d0e32d8b213137ab6b663e.tar.gz
[media] vivid: move video loopback control to the capture device
This has been on my TODO list for some time now: the control that enables the video loopback was part of the controls of the video output device instead of the video capture device. In practice this was quite annoying since you expect it at the capture side since that's where you want to make the decision whether to use the TPG or looped video. This patch moves the control from the output to the capture side. Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Diffstat (limited to 'Documentation/video4linux')
-rw-r--r--Documentation/video4linux/vivid.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/video4linux/vivid.txt b/Documentation/video4linux/vivid.txt
index 0c1b3a6..e35d376 100644
--- a/Documentation/video4linux/vivid.txt
+++ b/Documentation/video4linux/vivid.txt
@@ -895,7 +895,7 @@ Section 10.1: Video and Sliced VBI looping
The way to enable video/VBI looping is currently fairly crude. A 'Loop Video'
control is available in the "Vivid" control class of the video
-output and VBI output devices. When checked the video looping will be enabled.
+capture and VBI capture devices. When checked the video looping will be enabled.
Once enabled any video S-Video or HDMI input will show a static test pattern
until the video output has started. At that time the video output will be
looped to the video input provided that:
OpenPOWER on IntegriCloud