1 .. -*- coding: utf-8; mode: rst -*-
3 .. _VIDIOC_DV_TIMINGS_CAP:
5 *********************************************************
6 ioctl VIDIOC_DV_TIMINGS_CAP, VIDIOC_SUBDEV_DV_TIMINGS_CAP
7 *********************************************************
12 VIDIOC_DV_TIMINGS_CAP - VIDIOC_SUBDEV_DV_TIMINGS_CAP - The capabilities of the Digital Video receiver/transmitter
18 .. cpp:function:: int ioctl( int fd, int request, struct v4l2_dv_timings_cap *argp )
25 File descriptor returned by :ref:`open() <func-open>`.
28 VIDIOC_DV_TIMINGS_CAP, VIDIOC_SUBDEV_DV_TIMINGS_CAP
36 To query the capabilities of the DV receiver/transmitter applications
37 initialize the ``pad`` field to 0, zero the reserved array of struct
38 :ref:`v4l2_dv_timings_cap <v4l2-dv-timings-cap>` and call the
39 ``VIDIOC_DV_TIMINGS_CAP`` ioctl on a video node and the driver will fill
42 .. note:: Drivers may return different values after
43 switching the video input or output.
45 When implemented by the driver DV capabilities of subdevices can be
46 queried by calling the ``VIDIOC_SUBDEV_DV_TIMINGS_CAP`` ioctl directly
47 on a subdevice node. The capabilities are specific to inputs (for DV
48 receivers) or outputs (for DV transmitters), applications must specify
49 the desired pad number in the struct
50 :ref:`v4l2_dv_timings_cap <v4l2-dv-timings-cap>` ``pad`` field and
51 zero the ``reserved`` array. Attempts to query capabilities on a pad
52 that doesn't support them will return an ``EINVAL`` error code.
55 .. _v4l2-bt-timings-cap:
57 .. flat-table:: struct v4l2_bt_timings_cap
69 - Minimum width of the active video in pixels.
77 - Maximum width of the active video in pixels.
85 - Minimum height of the active video in lines.
93 - Maximum height of the active video in lines.
101 - Minimum pixelclock frequency in Hz.
109 - Maximum pixelclock frequency in Hz.
117 - The video standard(s) supported by the hardware. See
118 :ref:`dv-bt-standards` for a list of standards.
126 - Several flags giving more information about the capabilities. See
127 :ref:`dv-bt-cap-capabilities` for a description of the flags.
135 - Reserved for future extensions. Drivers must set the array to
140 .. _v4l2-dv-timings-cap:
142 .. flat-table:: struct v4l2_dv_timings_cap
154 - Type of DV timings as listed in :ref:`dv-timing-types`.
162 - Pad number as reported by the media controller API. This field is
163 only used when operating on a subdevice node. When operating on a
164 video node applications must set this field to zero.
172 - Reserved for future extensions. Drivers and applications must set
185 - struct :ref:`v4l2_bt_timings_cap <v4l2-bt-timings-cap>`
189 - BT.656/1120 timings capabilities of the hardware.
202 .. _dv-bt-cap-capabilities:
204 .. flat-table:: DV BT Timing capabilities
222 - ``V4L2_DV_BT_CAP_INTERLACED``
224 - Interlaced formats are supported.
228 - ``V4L2_DV_BT_CAP_PROGRESSIVE``
230 - Progressive formats are supported.
234 - ``V4L2_DV_BT_CAP_REDUCED_BLANKING``
236 - CVT/GTF specific: the timings can make use of reduced blanking
237 (CVT) or the 'Secondary GTF' curve (GTF).
241 - ``V4L2_DV_BT_CAP_CUSTOM``
243 - Can support non-standard timings, i.e. timings not belonging to
244 the standards set in the ``standards`` field.
250 On success 0 is returned, on error -1 and the ``errno`` variable is set
251 appropriately. The generic error codes are described at the
252 :ref:`Generic Error Codes <gen-errors>` chapter.