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, VIDIOC_DV_TIMINGS_CAP, struct v4l2_dv_timings_cap *argp )
19 :name: VIDIOC_DV_TIMINGS_CAP
21 .. c:function:: int ioctl( int fd, VIDIOC_SUBDEV_DV_TIMINGS_CAP, struct v4l2_dv_timings_cap *argp )
22 :name: VIDIOC_SUBDEV_DV_TIMINGS_CAP
29 File descriptor returned by :ref:`open() <func-open>`.
37 To query the capabilities of the DV receiver/transmitter applications
38 initialize the ``pad`` field to 0, zero the reserved array of struct
39 :c:type:`v4l2_dv_timings_cap` and call the
40 ``VIDIOC_DV_TIMINGS_CAP`` ioctl on a video node and the driver will fill
45 Drivers may return different values after
46 switching the video input or output.
48 When implemented by the driver DV capabilities of subdevices can be
49 queried by calling the ``VIDIOC_SUBDEV_DV_TIMINGS_CAP`` ioctl directly
50 on a subdevice node. The capabilities are specific to inputs (for DV
51 receivers) or outputs (for DV transmitters), applications must specify
52 the desired pad number in the struct
53 :c:type:`v4l2_dv_timings_cap` ``pad`` field and
54 zero the ``reserved`` array. Attempts to query capabilities on a pad
55 that doesn't support them will return an ``EINVAL`` error code.
58 .. tabularcolumns:: |p{1.2cm}|p{3.0cm}|p{13.3cm}|
60 .. c:type:: v4l2_bt_timings_cap
62 .. flat-table:: struct v4l2_bt_timings_cap
74 - Minimum width of the active video in pixels.
82 - Maximum width of the active video in pixels.
90 - Minimum height of the active video in lines.
98 - Maximum height of the active video in lines.
106 - Minimum pixelclock frequency in Hz.
114 - Maximum pixelclock frequency in Hz.
122 - The video standard(s) supported by the hardware. See
123 :ref:`dv-bt-standards` for a list of standards.
131 - Several flags giving more information about the capabilities. See
132 :ref:`dv-bt-cap-capabilities` for a description of the flags.
140 - Reserved for future extensions.
141 Drivers must set the array to zero.
145 .. tabularcolumns:: |p{1.0cm}|p{3.5cm}|p{3.5cm}|p{9.5cm}|
147 .. c:type:: v4l2_dv_timings_cap
149 .. flat-table:: struct v4l2_dv_timings_cap
161 - Type of DV timings as listed in :ref:`dv-timing-types`.
169 - Pad number as reported by the media controller API. This field is
170 only used when operating on a subdevice node. When operating on a
171 video node applications must set this field to zero.
179 - Reserved for future extensions.
181 Drivers and applications must set the array to zero.
193 - struct :c:type:`v4l2_bt_timings_cap`
197 - BT.656/1120 timings capabilities of the hardware.
208 .. tabularcolumns:: |p{7.0cm}|p{10.5cm}|
210 .. _dv-bt-cap-capabilities:
212 .. flat-table:: DV BT Timing capabilities
230 - ``V4L2_DV_BT_CAP_INTERLACED``
232 - Interlaced formats are supported.
236 - ``V4L2_DV_BT_CAP_PROGRESSIVE``
238 - Progressive formats are supported.
242 - ``V4L2_DV_BT_CAP_REDUCED_BLANKING``
244 - CVT/GTF specific: the timings can make use of reduced blanking
245 (CVT) or the 'Secondary GTF' curve (GTF).
249 - ``V4L2_DV_BT_CAP_CUSTOM``
251 - Can support non-standard timings, i.e. timings not belonging to
252 the standards set in the ``standards`` field.
258 On success 0 is returned, on error -1 and the ``errno`` variable is set
259 appropriately. The generic error codes are described at the
260 :ref:`Generic Error Codes <gen-errors>` chapter.