diff options
| author | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2016-07-10 11:57:43 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2016-07-10 12:06:28 -0300 |
| commit | 706f8a9975cb8889742d1f606ff466205ed29805 (patch) | |
| tree | 53f11f25ecbab359cfa29e56c0effff67e4c0500 /Documentation/media/uapi/v4l/vidioc-query-dv-timings.rst | |
| parent | fed7b888f69f70fc35c184677b2e8f59cb3945cb (diff) | |
| download | op-kernel-dev-706f8a9975cb8889742d1f606ff466205ed29805.zip op-kernel-dev-706f8a9975cb8889742d1f606ff466205ed29805.tar.gz | |
[media] doc-rst: improve display of notes and warnings
There are several notes and warning mesages in the middle of
the media docbook. Use the ReST tags for that, as it makes
them visually better and hightlights them.
While here, modify a few ones to make them clearer.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'Documentation/media/uapi/v4l/vidioc-query-dv-timings.rst')
| -rw-r--r-- | Documentation/media/uapi/v4l/vidioc-query-dv-timings.rst | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/Documentation/media/uapi/v4l/vidioc-query-dv-timings.rst b/Documentation/media/uapi/v4l/vidioc-query-dv-timings.rst index 338b80d..416d8d6 100644 --- a/Documentation/media/uapi/v4l/vidioc-query-dv-timings.rst +++ b/Documentation/media/uapi/v4l/vidioc-query-dv-timings.rst @@ -39,16 +39,16 @@ similar to sensing the video standard. To do so, applications call :ref:`v4l2_dv_timings <v4l2-dv-timings>`. Once the hardware detects the timings, it will fill in the timings structure. -Please note that drivers shall *not* switch timings automatically if new -timings are detected. Instead, drivers should send the -``V4L2_EVENT_SOURCE_CHANGE`` event (if they support this) and expect -that userspace will take action by calling :ref:`VIDIOC_QUERY_DV_TIMINGS`. -The reason is that new timings usually mean different buffer sizes as -well, and you cannot change buffer sizes on the fly. In general, -applications that receive the Source Change event will have to call -:ref:`VIDIOC_QUERY_DV_TIMINGS`, and if the detected timings are valid they -will have to stop streaming, set the new timings, allocate new buffers -and start streaming again. +.. note:: Drivers shall *not* switch timings automatically if new + timings are detected. Instead, drivers should send the + ``V4L2_EVENT_SOURCE_CHANGE`` event (if they support this) and expect + that userspace will take action by calling :ref:`VIDIOC_QUERY_DV_TIMINGS`. + The reason is that new timings usually mean different buffer sizes as + well, and you cannot change buffer sizes on the fly. In general, + applications that receive the Source Change event will have to call + :ref:`VIDIOC_QUERY_DV_TIMINGS`, and if the detected timings are valid they + will have to stop streaming, set the new timings, allocate new buffers + and start streaming again. If the timings could not be detected because there was no signal, then ENOLINK is returned. If a signal was detected, but it was unstable and |
