ioctl VIDIOC_DV_TIMINGS_CAP, VIDIOC_SUBDEV_DV_TIMINGS_CAP
&manvol;
VIDIOC_DV_TIMINGS_CAPVIDIOC_SUBDEV_DV_TIMINGS_CAPThe capabilities of the Digital Video receiver/transmitterint ioctlint fdint requeststruct v4l2_dv_timings_cap *argpArgumentsfd&fd;requestVIDIOC_DV_TIMINGS_CAP, VIDIOC_SUBDEV_DV_TIMINGS_CAPargpDescriptionExperimentalThis is an experimental
interface and may change in the future.To query the capabilities of the DV receiver/transmitter applications
can 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. Attempts to query capabilities on a pad that doesn't support them will
return an &EINVAL;.
struct v4l2_bt_timings_cap
&cs-str;
__u32min_widthMinimum width of the active video in pixels.__u32max_widthMaximum width of the active video in pixels.__u32min_heightMinimum height of the active video in lines.__u32max_heightMaximum height of the active video in lines.__u64min_pixelclockMinimum pixelclock frequency in Hz.__u64max_pixelclockMaximum pixelclock frequency in Hz.__u32standardsThe video standard(s) supported by the hardware.
See for a list of standards.__u32capabilitiesSeveral flags giving more information about the capabilities.
See for a description of the flags.
__u32reserved[16]Reserved for future extensions. Drivers must set the array to zero.
struct v4l2_dv_timings_cap
&cs-str;
__u32typeType of DV timings as listed in .__u32padPad 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.__u32reserved[2]Reserved for future extensions. Drivers must set the array to zero.union&v4l2-bt-timings-cap;btBT.656/1120 timings capabilities of the hardware.__u32raw_data[32]
DV BT Timing capabilities
&cs-str;
FlagDescriptionV4L2_DV_BT_CAP_INTERLACEDInterlaced formats are supported.
V4L2_DV_BT_CAP_PROGRESSIVEProgressive formats are supported.
V4L2_DV_BT_CAP_REDUCED_BLANKINGCVT/GTF specific: the timings can make use of reduced blanking (CVT)
or the 'Secondary GTF' curve (GTF).
V4L2_DV_BT_CAP_CUSTOMCan support non-standard timings, i.e. timings not belonging to the
standards set in the standards field.