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 .. c: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
44 Drivers may return different values after
45 switching the video input or output.
47 When implemented by the driver DV capabilities of subdevices can be
48 queried by calling the ``VIDIOC_SUBDEV_DV_TIMINGS_CAP`` ioctl directly
49 on a subdevice node. The capabilities are specific to inputs (for DV
50 receivers) or outputs (for DV transmitters), applications must specify
51 the desired pad number in the struct
52 :ref:`v4l2_dv_timings_cap <v4l2-dv-timings-cap>` ``pad`` field and
53 zero the ``reserved`` array. Attempts to query capabilities on a pad
54 that doesn't support them will return an ``EINVAL`` error code.
57 .. tabularcolumns:: |p{1.2cm}|p{3.0cm}|p{13.3cm}|
59 .. _v4l2-bt-timings-cap:
61 .. flat-table:: struct v4l2_bt_timings_cap
73 - Minimum width of the active video in pixels.
81 - Maximum width of the active video in pixels.
89 - Minimum height of the active video in lines.
97 - Maximum height of the active video in lines.
105 - Minimum pixelclock frequency in Hz.
113 - Maximum pixelclock frequency in Hz.
121 - The video standard(s) supported by the hardware. See
122 :ref:`dv-bt-standards` for a list of standards.
130 - Several flags giving more information about the capabilities. See
131 :ref:`dv-bt-cap-capabilities` for a description of the flags.
139 - Reserved for future extensions.
140 Drivers must set the array to zero.
144 .. tabularcolumns:: |p{1.0cm}|p{3.5cm}|p{3.5cm}|p{9.5cm}|
146 .. _v4l2-dv-timings-cap:
148 .. flat-table:: struct v4l2_dv_timings_cap
160 - Type of DV timings as listed in :ref:`dv-timing-types`.
168 - Pad number as reported by the media controller API. This field is
169 only used when operating on a subdevice node. When operating on a
170 video node applications must set this field to zero.
178 - Reserved for future extensions.
180 Drivers and applications must set the array to zero.
192 - struct :ref:`v4l2_bt_timings_cap <v4l2-bt-timings-cap>`
196 - BT.656/1120 timings capabilities of the hardware.
207 .. tabularcolumns:: |p{7.0cm}|p{10.5cm}|
209 .. _dv-bt-cap-capabilities:
211 .. flat-table:: DV BT Timing capabilities
229 - ``V4L2_DV_BT_CAP_INTERLACED``
231 - Interlaced formats are supported.
235 - ``V4L2_DV_BT_CAP_PROGRESSIVE``
237 - Progressive formats are supported.
241 - ``V4L2_DV_BT_CAP_REDUCED_BLANKING``
243 - CVT/GTF specific: the timings can make use of reduced blanking
244 (CVT) or the 'Secondary GTF' curve (GTF).
248 - ``V4L2_DV_BT_CAP_CUSTOM``
250 - Can support non-standard timings, i.e. timings not belonging to
251 the standards set in the ``standards`` field.
257 On success 0 is returned, on error -1 and the ``errno`` variable is set
258 appropriately. The generic error codes are described at the
259 :ref:`Generic Error Codes <gen-errors>` chapter.