| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-ext-ctrls.rst | 13 …OC_S_EXT_CTRLS - VIDIOC_TRY_EXT_CTRLS - Get or set the value of several controls, try control valu…
42 These ioctls allow the caller to get or set multiple controls
44 :ref:`ctrl-class`) and all controls in the control array must belong
47 Applications must always fill in the ``count``, ``which``, ``controls``
51 by the ``controls`` fields.
53 To get the current value of a set of controls applications initialize
56 :ref:`VIDIOC_G_EXT_CTRLS <VIDIOC_G_EXT_CTRLS>` ioctl. String controls controls must also set the
57 ``string`` field. Controls of compound types
61 relevant for pointer-type controls like strings), then the driver will
75 To change the value of a set of controls applications initialize the
[all …]
|
| D | extended-controls.rst | 3 .. _extended-controls:
6 Extended Controls API
33 Controls, such as Camera Controls and FM Transmitter Controls. The
34 Extended Controls API as well as all Extended Controls classes are
45 on arrays of controls (as opposed to the
49 several controls at once.
54 controls in that array and a control class. Control classes are used to
55 group similar controls into a single class. For example, control class
56 ``V4L2_CTRL_CLASS_USER`` contains all user controls (i. e. all controls
58 ioctl). Control class ``V4L2_CTRL_CLASS_MPEG`` contains all controls
[all …]
|
| D | control.rst | 6 User Controls
9 Devices typically have a number of user-settable controls such as
12 different controls available, and furthermore, the range of possible
15 user interface for these controls that will work correctly with any
18 All controls are accessed using an ID value. V4L2 defines several IDs
20 controls using ``V4L2_CID_PRIVATE_BASE`` [#f1]_ and higher values. The
25 Generally applications should present controls to the user without
30 to change a few controls programmatically, for example to mute a device
33 Drivers may enumerate different controls after switching the current
48 V4L2 specifies an event mechanism to notify applications when controls
[all …]
|
| D | vidioc-queryctrl.rst | 13 VIDIOC_QUERYCTRL - VIDIOC_QUERY_EXT_CTRL - VIDIOC_QUERYMENU - Enumerate controls and menu control i…
47 It is possible to enumerate controls by calling ``VIDIOC_QUERYCTRL``
51 controls, which are not defined in this specification, by starting at
62 can be specified to enumerate all compound controls (i.e. controls with
64 controls that contain more than one value). Specify both
66 order to enumerate all controls, compound or not. Drivers which do not
70 support controls that can use compound types, and to expose additional
78 Additional information is required for menu controls: the names of the
150 the user can change controls by keyboard or GUI buttons, rather
160 for other types of controls.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | extended-controls.rst | 3 .. _extended-controls:
6 Extended Controls API
33 Controls, such as Camera Controls and FM Transmitter Controls. The
34 Extended Controls API as well as all Extended Controls classes are
45 on arrays of controls (as opposed to the
49 several controls at once.
54 controls in that array and a control class. Control classes are used to
55 group similar controls into a single class. For example, control class
56 ``V4L2_CTRL_CLASS_USER`` contains all user controls (i. e. all controls
58 ioctl). Control class ``V4L2_CTRL_CLASS_CODEC`` contains controls
[all …]
|
| D | vidioc-g-ext-ctrls.rst | 13 …OC_S_EXT_CTRLS - VIDIOC_TRY_EXT_CTRLS - Get or set the value of several controls, try control valu…
42 These ioctls allow the caller to get or set multiple controls
44 :ref:`ctrl-class`) and all controls in the control array must belong
47 Applications must always fill in the ``count``, ``which``, ``controls``
51 by the ``controls`` fields.
53 To get the current value of a set of controls applications initialize
56 :ref:`VIDIOC_G_EXT_CTRLS <VIDIOC_G_EXT_CTRLS>` ioctl. String controls must also set the
57 ``string`` field. Controls of compound types
61 relevant for pointer-type controls like strings), then the driver will
75 To change the value of a set of controls applications initialize the
[all …]
|
| D | control.rst | 6 User Controls
9 Devices typically have a number of user-settable controls such as
12 different controls available, and furthermore, the range of possible
15 user interface for these controls that will work correctly with any
18 All controls are accessed using an ID value. V4L2 defines several IDs
20 controls using ``V4L2_CID_PRIVATE_BASE`` [#f1]_ and higher values. The
25 Generally applications should present controls to the user without
30 to change a few controls programmatically, for example to mute a device
33 Drivers may enumerate different controls after switching the current
48 V4L2 specifies an event mechanism to notify applications when controls
[all …]
|
| D | vidioc-queryctrl.rst | 13 VIDIOC_QUERYCTRL - VIDIOC_QUERY_EXT_CTRL - VIDIOC_QUERYMENU - Enumerate controls and menu control i…
47 It is possible to enumerate controls by calling ``VIDIOC_QUERYCTRL``
51 controls, which are not defined in this specification, by starting at
62 can be specified to enumerate all compound controls (i.e. controls with
64 controls that contain more than one value). Specify both
66 order to enumerate all controls, compound or not. Drivers which do not
70 support controls that can use compound types, and to expose additional
78 Additional information is required for menu controls: the names of the
150 the user can change controls by keyboard or GUI buttons, rather
160 for other types of controls.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/media/ |
| D | v4l2-controls.rst | 3 V4L2 Controls
10 implement correctly in drivers. But much of the code needed to handle controls
26 V4L2 specification with respect to controls in a central place. And to make
43 :c:type:`v4l2_ctrl_handler` is the object that keeps track of controls. It
45 references to controls, possibly to controls owned by other handlers.
89 The second argument is a hint telling the function how many controls this
114 2) Add controls:
116 You add non-menu controls by calling :c:func:`v4l2_ctrl_new_std`:
124 Menu and integer menu controls are added by calling
133 Menu controls with a driver specific menu are added by calling
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/media/ |
| D | v4l2-controls.rst | 3 V4L2 Controls
10 implement correctly in drivers. But much of the code needed to handle controls
26 V4L2 specification with respect to controls in a central place. And to make
43 :c:type:`v4l2_ctrl_handler` is the object that keeps track of controls. It
45 references to controls, possibly to controls owned by other handlers.
89 The second argument is a hint telling the function how many controls this
114 2) Add controls:
116 You add non-menu controls by calling :c:func:`v4l2_ctrl_new_std`:
124 Menu and integer menu controls are added by calling
133 Menu controls with a driver specific menu are added by calling
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/drivers/ |
| D | uvcvideo.rst | 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
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/drivers/ |
| D | uvcvideo.rst | 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
[all …]
|
| /kernel/linux/linux-6.6/drivers/reset/ |
| D | reset-ti-syscon.c | 43 * @controls: array of reset controls
44 * @nr_controls: number of controls in control array
49 struct ti_syscon_reset_control *controls; member
76 control = &data->controls[id]; in ti_syscon_reset_assert()
107 control = &data->controls[id]; in ti_syscon_reset_deassert()
140 control = &data->controls[id]; in ti_syscon_reset_status()
166 struct ti_syscon_reset_control *controls; in ti_syscon_reset_probe() local
184 controls = devm_kcalloc(dev, nr_controls, sizeof(*controls), in ti_syscon_reset_probe()
186 if (!controls) in ti_syscon_reset_probe()
190 controls[i].assert_offset = be32_to_cpup(list++); in ti_syscon_reset_probe()
[all …]
|
| /kernel/linux/linux-5.10/drivers/reset/ |
| D | reset-ti-syscon.c | 51 * @controls: array of reset controls
52 * @nr_controls: number of controls in control array
57 struct ti_syscon_reset_control *controls; member
84 control = &data->controls[id]; in ti_syscon_reset_assert()
115 control = &data->controls[id]; in ti_syscon_reset_deassert()
148 control = &data->controls[id]; in ti_syscon_reset_status()
174 struct ti_syscon_reset_control *controls; in ti_syscon_reset_probe() local
192 controls = devm_kcalloc(dev, nr_controls, sizeof(*controls), in ti_syscon_reset_probe()
194 if (!controls) in ti_syscon_reset_probe()
198 controls[i].assert_offset = be32_to_cpup(list++); in ti_syscon_reset_probe()
[all …]
|
| /kernel/linux/linux-5.10/include/media/ |
| D | v4l2-ctrls.h | 3 * V4L2 controls support header.
104 * for volatile (and usually read-only) controls such as a control
112 * one else can access controls owned by that handler.
160 * @ncontrols: Number of controls in cluster array.
199 * @step: The control's step value for non-menu controls.
204 * @menu_skip_mask: The control's skip mask for menu controls. This makes it
231 * through a pointer (for compound controls only).
303 * the control has been applied. This prevents applying controls
304 * from a cluster with multiple controls twice (when the first
316 * keep a sorted-by-control-ID list of all controls, while the next pointer
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-fs-f2fs | 4 Description: Controls the maximum sleep time for gc_thread. Time
10 Description: Controls the minimum sleep time for gc_thread. Time
16 Description: Controls the default sleep time for gc_thread. Time
22 Description: Controls the victim selection policy for garbage collection.
34 Description: This parameter controls the number of prefree segments to be
50 Description: Controls the in-place-update policy.
68 Description: Controls the FS utilization condition for the in-place-update
74 Description: Controls the dirty page count condition for the in-place-update
80 Description: Controls the dirty page count condition for batched sequential
86 Description: Controls the dirty page count condition for redefining hot data.
[all …]
|
| D | sysfs-driver-toshiba_acpi | 5 Description: This file controls the keyboard backlight operation mode, valid
24 Description: This file controls the timeout of the keyboard backlight
44 Description: This files controls the status of the touchpad and pointing
83 Description: This file controls the USB Sleep & Charge charging mode, which
102 Description: This file controls the USB Sleep Functions under battery, and
120 Description: This file controls the USB Rapid Charge state, which can be:
133 Description: This file controls the Sleep & Music state, which values can be:
154 Description: This file controls the state of the internal fan, valid
164 Description: This file controls the Special Functions (hotkeys) operation
182 Description: This file controls whether the laptop should turn ON whenever
[all …]
|
| /kernel/linux/linux-6.6/include/media/ |
| D | v4l2-ctrls.h | 3 * V4L2 controls support header.
112 * for volatile (and usually read-only) controls such as a control
120 * one else can access controls owned by that handler.
166 * @ncontrols: Number of controls in cluster array.
207 * @step: The control's step value for non-menu controls.
215 * @menu_skip_mask: The control's skip mask for menu controls. This makes it
247 * through a pointer (for compound controls only).
323 * the control has been applied. This prevents applying controls
324 * from a cluster with multiple controls twice (when the first
346 * keep a sorted-by-control-ID list of all controls, while the next pointer
[all …]
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | v4l2-controls.h | 3 * Video for Linux Two controls header file
56 #define V4L2_CTRL_CLASS_USER 0x00980000 /* Old-style 'user' controls */
57 #define V4L2_CTRL_CLASS_MPEG 0x00990000 /* MPEG-compression controls */
58 #define V4L2_CTRL_CLASS_CAMERA 0x009a0000 /* Camera class controls */
59 #define V4L2_CTRL_CLASS_FM_TX 0x009b0000 /* FM Modulator controls */
60 #define V4L2_CTRL_CLASS_FLASH 0x009c0000 /* Camera flash controls */
61 #define V4L2_CTRL_CLASS_JPEG 0x009d0000 /* JPEG-compression controls */
62 #define V4L2_CTRL_CLASS_IMAGE_SOURCE 0x009e0000 /* Image source controls */
63 #define V4L2_CTRL_CLASS_IMAGE_PROC 0x009f0000 /* Image processing controls */
64 #define V4L2_CTRL_CLASS_DV 0x00a00000 /* Digital Video controls */
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-fs-f2fs | 4 Description: Controls the maximum sleep time for gc_thread. Time
10 Description: Controls the minimum sleep time for gc_thread. Time
16 Description: Controls the default sleep time for gc_thread. Time
22 Description: Controls the victim selection policy for garbage collection.
34 Description: This parameter controls the number of prefree segments to be
49 Description: Controls the in-place-update policy.
75 Description: Controls the FS utilization condition for the in-place-update
81 Description: Controls the dirty page count condition for the in-place-update
87 Description: Controls the dirty page count condition for batched sequential
93 Description: Controls the dirty page count condition for redefining hot data.
[all …]
|
| D | sysfs-driver-toshiba_acpi | 5 Description: This file controls the keyboard backlight operation mode, valid
24 Description: This file controls the timeout of the keyboard backlight
44 Description: This files controls the status of the touchpad and pointing
83 Description: This file controls the USB Sleep & Charge charging mode, which
102 Description: This file controls the USB Sleep Functions under battery, and
120 Description: This file controls the USB Rapid Charge state, which can be:
133 Description: This file controls the Sleep & Music state, which values can be:
154 Description: This file controls the state of the internal fan, valid
164 Description: This file controls the Special Functions (hotkeys) operation
182 Description: This file controls whether the laptop should turn ON whenever
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/media/ |
| D | vivid.rst | 25 - Working brightness, contrast, saturation and hue controls
204 select this through controls.
236 select this through controls.
276 if set disable the error injecting controls. This option is
278 exercise all controls including a control like 'Disconnect' which
284 controls that select crop, compose and scale behavior are also
351 controls 'Standard Signal Mode' and 'Standard' determine what
526 The FM receiver supports RDS as well, both using 'Block I/O' and 'Controls'
527 modes. In the 'Controls' mode the RDS information is stored in read-only
528 controls. These controls are updated every time the frequency is changed,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | vivid.rst | 25 - Working brightness, contrast, saturation and hue controls
204 select this through controls.
236 select this through controls.
276 if set disable the error injecting controls. This option is
278 exercise all controls including a control like 'Disconnect' which
284 controls that select crop, compose and scale behavior are also
351 controls 'Standard Signal Mode' and 'Standard' determine what
526 The FM receiver supports RDS as well, both using 'Block I/O' and 'Controls'
527 modes. In the 'Controls' mode the RDS information is stored in read-only
528 controls. These controls are updated every time the frequency is changed,
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | reset.rst | 18 controller devices to register their reset controls to provide them to the
41 In more complicated reset controls, a single trigger action can launch a
46 A hardware module that provides a number of reset controls to control a
59 controls.
63 When requesting reset controls, consumers can use symbolic names for their
75 The distinction between shared and exclusive reset controls is made at the time
96 For shared reset controls, calls to the two functions must be balanced.
101 Consumer drivers using shared reset controls should assume that the reset line
115 The reset controller API allows requesting self-deasserting reset controls as
120 For shared reset controls, calls to the two functions must be balanced.
[all …]
|
| /kernel/linux/linux-6.6/drivers/media/v4l2-core/ |
| D | v4l2-ctrls-defs.c | 3 * V4L2 controls framework control definitions.
790 /* USER controls */ in v4l2_ctrl_get_name()
791 /* Keep the order of the 'case's the same as in v4l2-controls.h! */ in v4l2_ctrl_get_name()
792 case V4L2_CID_USER_CLASS: return "User Controls"; in v4l2_ctrl_get_name()
836 * Codec controls in v4l2_ctrl_get_name()
838 * The MPEG controls are applicable to all codec controls in v4l2_ctrl_get_name()
843 case V4L2_CID_CODEC_CLASS: return "Codec Controls"; in v4l2_ctrl_get_name()
976 /* VPX controls */ in v4l2_ctrl_get_name()
992 /* HEVC controls */ in v4l2_ctrl_get_name()
1045 /* AV1 controls */ in v4l2_ctrl_get_name()
[all …]
|