Lines Matching refs:control

25 control enumeration.
37 control mappings at runtime. These allow for individual XU controls or byte
41 triggers a read or write of the associated XU control.
43 The ioctl used to create these control mappings is called UVCIOC_CTRL_MAP.
45 beforehand (UVCIOC_CTRL_ADD) to pass XU control information to the UVC driver.
53 3. Driver specific XU control interface
61 directly map to the low-level UVC control requests.
63 In order to make such a request the UVC unit ID of the control's extension unit
64 and the control selector need to be known. This information either needs to be
69 Unless the control size is already known it is necessary to first make a
72 UVC_GET_CUR or UVC_SET_CUR are valid requests for a given control, a
87 The API doesn't currently provide a fine-grained access control facility. The
102 ---- UVCIOC_CTRL_MAP - Map a UVC control to a V4L2 control ----
107 This ioctl creates a mapping between a UVC control or part of a UVC
108 control and a V4L2 control. Once mappings are defined, userspace
109 applications can access vendor-defined UVC control through the V4L2
110 control API.
113 structure with information about an existing UVC control defined with
114 UVCIOC_CTRL_ADD and a new V4L2 control.
116 A UVC control can be mapped to several V4L2 controls. For instance,
117 a UVC pan/tilt control could be mapped to separate pan and tilt V4L2
118 controls. The UVC control is divided into non overlapping fields using
120 V4L2 control.
134 No such UVC control.
136 The requested offset and size would overflow the UVC control.
143 __u32 id V4L2 control identifier
144 __u8 name[32] V4L2 control name
146 __u8 selector UVC control selector
147 __u8 size V4L2 control size (in bits)
148 __u8 offset V4L2 control offset (in bits)
150 v4l2_type V4L2 control type
152 data_type UVC control data type
165 UVC_CTRL_DATA_TYPE_RAW Raw control (byte array)
173 ---- UVCIOC_CTRL_QUERY - Query a UVC XU control ----
178 This ioctl queries a UVC XU control identified by its extension unit ID
179 and control selector.
182 correspond to the low-level control requests described in the UVC
186 Obtain the current value of the control.
188 Obtain the minimum value of the control.
190 Obtain the maximum value of the control.
192 Obtain the default value of the control.
194 Query the resolution of the control, i.e. the step size of the
195 allowed control values.
197 Query the size of the control in bytes.
199 Query the control information bitmap, which indicates whether
202 Update the value of the control.
205 control. Exceptions are the UVC_GET_LEN and UVC_GET_INFO queries, for
221 The device does not support the given control or the specified
228 The given request is not supported by the given control.