Lines Matching refs:controls

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