Lines Matching refs:controls

20 units (XUs). The Linux UVC driver supports extension unit controls (XU controls)
23   - through mappings of XU controls to V4L2 controls
26 The first one allows generic V4L2 applications to use XU controls by mapping
27 certain XU controls onto V4L2 controls, which then show up during ordinary
31 access XU controls but exposes the entire UVC XU concept to user space for
41 control mappings at runtime. These allow for individual XU controls or byte
42 ranges thereof to be mapped to new V4L2 controls. Such controls appear and
43 function exactly like normal V4L2 controls (i.e. the stock controls, such as
44 brightness, contrast, etc.). However, reading or writing of such a V4L2 controls
59 For applications that need to access XU controls directly, e.g. for testing
60 purposes, firmware upload, or accessing binary controls, a second mechanism to
61 access XU controls is provided in the form of a driver-specific ioctl, namely
101 In order to debug problems related to XU controls or controls in general it is
125 	A UVC control can be mapped to several V4L2 controls. For instance,
127 	controls. The UVC control is divided into non overlapping fields using
131 	For signed integer V4L2 controls the data_type field should be set to
167 		*menu_info	Array of menu entries (for menu controls only)
168 	__u32	menu_count	Number of menu entries (for menu controls only)