aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/DocBook/v4l/vidioc-subdev-g-crop.xml
blob: 06197323a8cc522c510dba5050d707e7c9f0c4c4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
<refentry id="vidioc-subdev-g-crop">
  <refmeta>
    <refentrytitle>ioctl VIDIOC_SUBDEV_G_CROP, VIDIOC_SUBDEV_S_CROP</refentrytitle>
    &manvol;
  </refmeta>

  <refnamediv>
    <refname>VIDIOC_SUBDEV_G_CROP</refname>
    <refname>VIDIOC_SUBDEV_S_CROP</refname>
    <refpurpose>Get or set the crop rectangle on a subdev pad</refpurpose>
  </refnamediv>

  <refsynopsisdiv>
    <funcsynopsis>
      <funcprototype>
	<funcdef>int <function>ioctl</function></funcdef>
	<paramdef>int <parameter>fd</parameter></paramdef>
	<paramdef>int <parameter>request</parameter></paramdef>
	<paramdef>struct v4l2_subdev_crop *<parameter>argp</parameter></paramdef>
      </funcprototype>
    </funcsynopsis>
    <funcsynopsis>
      <funcprototype>
	<funcdef>int <function>ioctl</function></funcdef>
	<paramdef>int <parameter>fd</parameter></paramdef>
	<paramdef>int <parameter>request</parameter></paramdef>
	<paramdef>const struct v4l2_subdev_crop *<parameter>argp</parameter></paramdef>
      </funcprototype>
    </funcsynopsis>
  </refsynopsisdiv>

  <refsect1>
    <title>Arguments</title>

    <variablelist>
      <varlistentry>
	<term><parameter>fd</parameter></term>
	<listitem>
	  <para>&fd;</para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><parameter>request</parameter></term>
	<listitem>
	  <para>VIDIOC_SUBDEV_G_CROP, VIDIOC_SUBDEV_S_CROP</para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><parameter>argp</parameter></term>
	<listitem>
	  <para></para>
	</listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1>
    <title>Description</title>

    <note>
      <title>Experimental</title>
      <para>This is an <link linkend="experimental">experimental</link>
      interface and may change in the future.</para>
    </note>

    <para>To retrieve the current crop rectangle applications set the
    <structfield>pad</structfield> field of a &v4l2-subdev-crop; to the
    desired pad number as reported by the media API and the
    <structfield>which</structfield> field to
    <constant>V4L2_SUBDEV_FORMAT_ACTIVE</constant>. They then call the
    <constant>VIDIOC_SUBDEV_G_CROP</constant> ioctl with a pointer to this
    structure. The driver fills the members of the <structfield>rect</structfield>
    field or returns &EINVAL; if the input arguments are invalid, or if cropping
    is not supported on the given pad.</para>

    <para>To change the current crop rectangle applications set both the
    <structfield>pad</structfield> and <structfield>which</structfield> fields
    and all members of the <structfield>rect</structfield> field. They then call
    the <constant>VIDIOC_SUBDEV_S_CROP</constant> ioctl with a pointer to this
    structure. The driver verifies the requested crop rectangle, adjusts it
    based on the hardware capabilities and configures the device. Upon return
    the &v4l2-subdev-crop; contains the current format as would be returned
    by a <constant>VIDIOC_SUBDEV_G_CROP</constant> call.</para>

    <para>Applications can query the device capabilities by setting the
    <structfield>which</structfield> to
    <constant>V4L2_SUBDEV_FORMAT_TRY</constant>. When set, 'try' crop
    rectangles are not applied to the device by the driver, but are mangled
    exactly as active crop rectangles and stored in the sub-device file handle.
    Two applications querying the same sub-device would thus not interact with
    each other.</para>

    <para>Drivers must not return an error solely because the requested crop
    rectangle doesn't match the device capabilities. They must instead modify
    the rectangle to match what the hardware can provide. The modified format
    should be as close as possible to the original request.</para>

    <table pgwide="1" frame="none" id="v4l2-subdev-crop">
      <title>struct <structname>v4l2_subdev_crop</structname></title>
      <tgroup cols="3">
        &cs-str;
	<tbody valign="top">
	  <row>
	    <entry>__u32</entry>
	    <entry><structfield>pad</structfield></entry>
	    <entry>Pad number as reported by the media framework.</entry>
	  </row>
	  <row>
	    <entry>__u32</entry>
	    <entry><structfield>which</structfield></entry>
	    <entry>Crop rectangle to get or set, from
	    &v4l2-subdev-format-whence;.</entry>
	  </row>
	  <row>
	    <entry>&v4l2-rect;</entry>
	    <entry><structfield>rect</structfield></entry>
	    <entry>Crop rectangle boundaries, in pixels.</entry>
	  </row>
	  <row>
	    <entry>__u32</entry>
	    <entry><structfield>reserved</structfield>[8]</entry>
	    <entry>Reserved for future extensions. Applications and drivers must
	    set the array to zero.</entry>
	  </row>
	</tbody>
      </tgroup>
    </table>
  </refsect1>

  <refsect1>
    &return-value;

    <variablelist>
      <varlistentry>
	<term><errorcode>EBUSY</errorcode></term>
	<listitem>
	  <para>The crop rectangle can't be changed because the pad is currently
	  busy. This can be caused, for instance, by an active video stream on
	  the pad. The ioctl must not be retried without performing another
	  action to fix the problem first. Only returned by
	  <constant>VIDIOC_SUBDEV_S_CROP</constant></para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><errorcode>EINVAL</errorcode></term>
	<listitem>
	  <para>The &v4l2-subdev-crop; <structfield>pad</structfield>
	  references a non-existing pad, the <structfield>which</structfield>
	  field references a non-existing format, or cropping is not supported
	  on the given subdev pad.</para>
	</listitem>
      </varlistentry>
    </variablelist>
  </refsect1>
</refentry>