7.26. ioctl VIDIOC_G_DV_TIMINGS, VIDIOC_S_DV_TIMINGS¶
7.26.1. Name¶
VIDIOC_G_DV_TIMINGS - VIDIOC_S_DV_TIMINGS - VIDIOC_SUBDEV_G_DV_TIMINGS - VIDIOC_SUBDEV_S_DV_TIMINGS - Get or set DV timings for input or output
7.26.2. Synopsis¶
-
VIDIOC_G_DV_TIMINGS¶
int ioctl(int fd, VIDIOC_G_DV_TIMINGS, struct v4l2_dv_timings *argp)
-
VIDIOC_S_DV_TIMINGS¶
int ioctl(int fd, VIDIOC_S_DV_TIMINGS, struct v4l2_dv_timings *argp)
-
VIDIOC_SUBDEV_G_DV_TIMINGS¶
int ioctl(int fd, VIDIOC_SUBDEV_G_DV_TIMINGS, struct v4l2_dv_timings *argp)
-
VIDIOC_SUBDEV_S_DV_TIMINGS¶
int ioctl(int fd, VIDIOC_SUBDEV_S_DV_TIMINGS, struct v4l2_dv_timings *argp)
7.26.3. Arguments¶
fd
File descriptor returned by
open()
.argp
Pointer to struct
v4l2_dv_timings
.
7.26.4. Description¶
To set DV timings for the input or output, applications use the
VIDIOC_S_DV_TIMINGS ioctl and to get the current timings,
applications use the VIDIOC_G_DV_TIMINGS ioctl. The detailed timing
information is filled in using the structure struct
v4l2_dv_timings
. These ioctls take a
pointer to the struct v4l2_dv_timings
structure as argument. If the ioctl is not supported or the timing
values are not correct, the driver returns EINVAL
error code.
Calling VIDIOC_SUBDEV_S_DV_TIMINGS
on a subdev device node that has been
registered in read-only mode is not allowed. An error is returned and the errno
variable is set to -EPERM
.
The linux/v4l2-dv-timings.h
header can be used to get the timings of
the formats in the CEA-861-E and VESA DMT standards. If
the current input or output does not support DV timings (e.g. if
ioctl VIDIOC_ENUMINPUT does not set the
V4L2_IN_CAP_DV_TIMINGS
flag), then ENODATA
error code is returned.
7.26.5. Return Value¶
On success 0 is returned, on error -1 and the errno
variable is set
appropriately. The generic error codes are described at the
Generic Error Codes chapter.
- EINVAL
This ioctl is not supported, or the VIDIOC_S_DV_TIMINGS parameter was unsuitable.
- ENODATA
Digital video timings are not supported for this input or output.
- EBUSY
The device is busy and therefore can not change the timings.
- EPERM
VIDIOC_SUBDEV_S_DV_TIMINGS
has been called on a read-only subdevice.
-
type v4l2_bt_timings¶
__u32 |
|
Width of the active video in pixels. |
__u32 |
|
Height of the active video frame in lines. So for interlaced
formats the height of the active video in each field is
|
__u32 |
|
Progressive ( |
__u32 |
|
This is a bit mask that defines polarities of sync signals. bit 0
( |
__u64 |
|
Pixel clock in Hz. Ex. 74.25MHz->74250000 |
__u32 |
|
Horizontal front porch in pixels |
__u32 |
|
Horizontal sync length in pixels |
__u32 |
|
Horizontal back porch in pixels |
__u32 |
|
Vertical front porch in lines. For interlaced formats this refers to the odd field (aka field 1). |
__u32 |
|
Vertical sync length in lines. For interlaced formats this refers to the odd field (aka field 1). |
__u32 |
|
Vertical back porch in lines. For interlaced formats this refers to the odd field (aka field 1). |
__u32 |
|
Vertical front porch in lines for the even field (aka field 2) of interlaced field formats. Must be 0 for progressive formats. |
__u32 |
|
Vertical sync length in lines for the even field (aka field 2) of interlaced field formats. Must be 0 for progressive formats. |
__u32 |
|
Vertical back porch in lines for the even field (aka field 2) of interlaced field formats. Must be 0 for progressive formats. |
__u32 |
|
The video standard(s) this format belongs to. This will be filled in by the driver. Applications must set this to 0. See DV BT Timing standards for a list of standards. |
__u32 |
|
Several flags giving more information about the format. See DV BT Timing flags for a description of the flags. |
struct |
|
The picture aspect if the pixels are not square. Only valid if the
|
__u8 |
|
The Video Identification Code according to the CEA-861 standard.
Only valid if the |
__u8 |
|
The Video Identification Code according to the HDMI standard.
Only valid if the |
__u8 |
|
Reserved for future extensions. Drivers and applications must set the array to zero. |
-
type v4l2_dv_timings¶
__u32 |
|
Type of DV timings as listed in DV Timing types. |
union { |
(anonymous) |
|
struct |
|
Timings defined by BT.656/1120 specifications |
__u32 |
|
|
} |
Timing type |
value |
Description |
|
0 |
BT.656/1120 timings |
Timing standard |
Description |
|
The timings follow the CEA-861 Digital TV Profile standard |
|
The timings follow the VESA Discrete Monitor Timings standard |
|
The timings follow the VESA Coordinated Video Timings standard |
|
The timings follow the VESA Generalized Timings Formula standard |
|
The timings follow the SDI Timings standard. There are no horizontal syncs/porches at all in this format. Total blanking timings must be set in hsync or vsync fields only. |
Flag |
Description |
|
CVT/GTF specific: the timings use reduced blanking (CVT) or the ‘Secondary GTF’ curve (GTF). In both cases the horizontal and/or vertical blanking intervals are reduced, allowing a higher resolution over the same bandwidth. This is a read-only flag, applications must not set this. |
|
CEA-861 specific: set for CEA-861 formats with a framerate that is a multiple of six. These formats can be optionally played at 1 / 1.001 speed to be compatible with 60 Hz based standards such as NTSC and PAL-M that use a framerate of 29.97 frames per second. If the transmitter can’t generate such frequencies, then the flag will also be cleared. This is a read-only flag, applications must not set this. |
|
CEA-861 specific: only valid for video transmitters or video
receivers that have the If the application sets this flag for a transmitter, then the pixelclock used to set up the transmitter is divided by 1.001 to make it compatible with NTSC framerates. If the transmitter can’t generate such frequencies, then the flag will be cleared. If a video receiver detects that the format uses a reduced framerate, then it will set this flag to signal this to the application. |
|
Specific to interlaced formats: if set, then the vertical frontporch of field 1 (aka the odd field) is really one half-line longer and the vertical backporch of field 2 (aka the even field) is really one half-line shorter, so each field has exactly the same number of half-lines. Whether half-lines can be detected or used depends on the hardware. |
|
If set, then this is a Consumer Electronics (CE) video format. Such formats differ from other formats (commonly called IT formats) in that if R’G’B’ encoding is used then by default the R’G’B’ values use limited range (i.e. 16-235) as opposed to full range (i.e. 0-255). All formats defined in CEA-861 except for the 640x480p59.94 format are CE formats. |
|
Some formats like SMPTE-125M have an interlaced signal with a odd total height. For these formats, if this flag is set, the first field has the extra line. Else, it is the second field. |
|
If set, then the picture_aspect field is valid. Otherwise assume that the pixels are square, so the picture aspect ratio is the same as the width to height ratio. |
|
If set, then the cea861_vic field is valid and contains the Video Identification Code as per the CEA-861 standard. |
|
If set, then the hdmi_vic field is valid and contains the Video Identification Code as per the HDMI standard (HDMI Vendor Specific InfoFrame). |
|
CEA-861 specific: only valid for video receivers, the flag is cleared by transmitters. If set, then the hardware can detect the difference between regular framerates and framerates reduced by 1000/1001. E.g.: 60 vs 59.94 Hz, 30 vs 29.97 Hz or 24 vs 23.976 Hz. |