|
|
@@ -55,8 +55,9 @@
|
|
|
interface and may change in the future.</para>
|
|
|
</note>
|
|
|
|
|
|
- <para>To query the capabilities of the DV receiver/transmitter applications
|
|
|
-can call the <constant>VIDIOC_DV_TIMINGS_CAP</constant> ioctl on a video node
|
|
|
+ <para>To query the capabilities of the DV receiver/transmitter applications initialize the
|
|
|
+<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
|
|
|
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
|
|
|
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; <structfield>pad</structfield>
|
|
|
-field. Attempts to query capabilities on a pad that doesn't support them will
|
|
|
-return an &EINVAL;.</para>
|
|
|
+field and zero the <structfield>reserved</structfield> array. Attempts to query
|
|
|
+capabilities on a pad that doesn't support them will return an &EINVAL;.</para>
|
|
|
|
|
|
<table pgwide="1" frame="none" id="v4l2-bt-timings-cap">
|
|
|
<title>struct <structname>v4l2_bt_timings_cap</structname></title>
|
|
|
@@ -145,7 +146,8 @@ return an &EINVAL;.</para>
|
|
|
<row>
|
|
|
<entry>__u32</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>
|
|
|
<entry>union</entry>
|