ioctl VIDIOC_DV_TIMINGS_CAP, VIDIOC_SUBDEV_DV_TIMINGS_CAP
&manvol;
VIDIOC_DV_TIMINGS_CAP
VIDIOC_SUBDEV_DV_TIMINGS_CAP
The capabilities of the Digital Video receiver/transmitter
int ioctl
int fd
int request
struct v4l2_dv_timings_cap *argp
Arguments
fd
&fd;
request
VIDIOC_DV_TIMINGS_CAP, VIDIOC_SUBDEV_DV_TIMINGS_CAP
argp
Description
To query the capabilities of the DV receiver/transmitter applications initialize the
pad field to 0, zero the reserved array of &v4l2-dv-timings-cap;
and call the VIDIOC_DV_TIMINGS_CAP ioctl on a video node
and the driver will fill in the structure. Note that drivers may return
different values after switching the video input or output.
When implemented by the driver DV capabilities of subdevices can be
queried by calling the VIDIOC_SUBDEV_DV_TIMINGS_CAP ioctl
directly on a subdevice node. The capabilities are specific to inputs (for DV
receivers) or outputs (for DV transmitters), applications must specify the
desired pad number in the &v4l2-dv-timings-cap; pad
field and zero the reserved array. Attempts to query
capabilities on a pad that doesn't support them will return an &EINVAL;.
struct v4l2_bt_timings_cap
&cs-str;
__u32
min_width
Minimum width of the active video in pixels.
__u32
max_width
Maximum width of the active video in pixels.
__u32
min_height
Minimum height of the active video in lines.
__u32
max_height
Maximum height of the active video in lines.
__u64
min_pixelclock
Minimum pixelclock frequency in Hz.
__u64
max_pixelclock
Maximum pixelclock frequency in Hz.
__u32
standards
The video standard(s) supported by the hardware.
See for a list of standards.
__u32
capabilities
Several flags giving more information about the capabilities.
See for a description of the flags.
__u32
reserved[16]
Reserved for future extensions. Drivers must set the array to zero.
struct v4l2_dv_timings_cap
&cs-str;
__u32
type
Type of DV timings as listed in .
__u32
pad
Pad number as reported by the media controller API. This field
is only used when operating on a subdevice node. When operating on a
video node applications must set this field to zero.
__u32
reserved[2]
Reserved for future extensions. Drivers and applications must
set the array to zero.
union
&v4l2-bt-timings-cap;
bt
BT.656/1120 timings capabilities of the hardware.
__u32
raw_data[32]
DV BT Timing capabilities
&cs-str;
Flag
Description
V4L2_DV_BT_CAP_INTERLACED
Interlaced formats are supported.
V4L2_DV_BT_CAP_PROGRESSIVE
Progressive formats are supported.
V4L2_DV_BT_CAP_REDUCED_BLANKING
CVT/GTF specific: the timings can make use of reduced blanking (CVT)
or the 'Secondary GTF' curve (GTF).
V4L2_DV_BT_CAP_CUSTOM
Can support non-standard timings, i.e. timings not belonging to the
standards set in the standards field.
&return-value;