Commit c5c63141 authored by Hans Verkuil's avatar Hans Verkuil Committed by Mauro Carvalho Chehab

[media] vidioc-dv-timings-cap.xml: explicitly state that pad and reserved should be zeroed

The DV_TIMINGS_CAP documentation didn't state clearly that the pad and
reserved fields should be zeroed by the application. For subdev pad can
be other values as well.

It also mistakenly said that only drivers would have to zero the reserved
field, that's not correct.
Signed-off-by: default avatarHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@osg.samsung.com>
parent 0c53fee9
...@@ -55,8 +55,9 @@ ...@@ -55,8 +55,9 @@
interface and may change in the future.</para> interface and may change in the future.</para>
</note> </note>
<para>To query the capabilities of the DV receiver/transmitter applications <para>To query the capabilities of the DV receiver/transmitter applications initialize the
can call the <constant>VIDIOC_DV_TIMINGS_CAP</constant> ioctl on a video node <structfield>pad</structfield> field to 0, zero the reserved array of &v4l2-dv-timings-cap;
and call the <constant>VIDIOC_DV_TIMINGS_CAP</constant> ioctl on a video node
and the driver will fill in the structure. Note that drivers may return and the driver will fill in the structure. Note that drivers may return
different values after switching the video input or output.</para> different values after switching the video input or output.</para>
...@@ -65,8 +66,8 @@ queried by calling the <constant>VIDIOC_SUBDEV_DV_TIMINGS_CAP</constant> ioctl ...@@ -65,8 +66,8 @@ queried by calling the <constant>VIDIOC_SUBDEV_DV_TIMINGS_CAP</constant> ioctl
directly on a subdevice node. The capabilities are specific to inputs (for DV directly on a subdevice node. The capabilities are specific to inputs (for DV
receivers) or outputs (for DV transmitters), applications must specify the receivers) or outputs (for DV transmitters), applications must specify the
desired pad number in the &v4l2-dv-timings-cap; <structfield>pad</structfield> desired pad number in the &v4l2-dv-timings-cap; <structfield>pad</structfield>
field. Attempts to query capabilities on a pad that doesn't support them will field and zero the <structfield>reserved</structfield> array. Attempts to query
return an &EINVAL;.</para> capabilities on a pad that doesn't support them will return an &EINVAL;.</para>
<table pgwide="1" frame="none" id="v4l2-bt-timings-cap"> <table pgwide="1" frame="none" id="v4l2-bt-timings-cap">
<title>struct <structname>v4l2_bt_timings_cap</structname></title> <title>struct <structname>v4l2_bt_timings_cap</structname></title>
...@@ -145,7 +146,8 @@ return an &EINVAL;.</para> ...@@ -145,7 +146,8 @@ return an &EINVAL;.</para>
<row> <row>
<entry>__u32</entry> <entry>__u32</entry>
<entry><structfield>reserved</structfield>[2]</entry> <entry><structfield>reserved</structfield>[2]</entry>
<entry>Reserved for future extensions. Drivers must set the array to zero.</entry> <entry>Reserved for future extensions. Drivers and applications must
set the array to zero.</entry>
</row> </row>
<row> <row>
<entry>union</entry> <entry>union</entry>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment