Searched full:controls (Results 1 – 25 of 479) sorted by relevance
12345678910>>...20
| /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 …]
|
| D | dev-stateless-decoder.rst | 45 codec-specific capability controls (such as H.264 profiles) to the set
55 formats may depend on the value of some codec-dependent controls.
56 The client is responsible for making sure that these controls are set
58 default values for these controls being used, and a returned set of formats
66 applicable, may be queried using their respective controls via
96 2. Call :c:func:`VIDIOC_S_EXT_CTRLS` to set all the controls (parsed headers,
137 ``OUTPUT`` format and currently set controls, even if more formats may be
239 controls relevant to the format being decoded.
242 controls that must be set on the request, depend on the active coded pixel
243 format and might be affected by codec-specific extended controls, as stated in
[all …]
|
| D | ext-ctrls-rf-tuner.rst | 3 .. _rf-tuner-controls:
9 The RF Tuner (RF_TUNER) class includes controls for common features of
18 without a metal box "silicon tuners". These controls are mostly
63 There may be both RF and LNA gain controls in the same device. The
82 located on output of RF tuner. It controls signal level of
|
| D | v4l2.rst | 185 V4L2_CID_COLORFX_CBCR control. Added camera controls
199 Added :ref:`JPEG compression control class. <jpeg-controls>`
243 Added documentation for string controls and for FM Transmitter controls.
260 capabilities. Added support for string controls.
267 controls V4L2_CID_ZOOM_ABSOLUTE, V4L2_CID_ZOOM_RELATIVE,
273 Added pixel formats Y16 and SBGGR16, new controls and a camera controls
285 Added the Video Output Overlay interface, new MPEG controls,
312 Added the description of extended controls by Hans Verkuil. Linked
|
| D | dev-radio.rst | 31 Radio devices can support :ref:`controls <control>`, and must support
43 Radio devices may have a couple audio controls (as discussed in
44 :ref:`control`) such as a volume control, possibly custom controls.
|
| D | ext-ctrls-image-process.rst | 3 .. _image-process-controls:
11 controls in this class affect processing the image, and do not control
37 control may be present in a different sub-device than the blanking controls
|
| /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 …]
|
| /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 …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-usb-devices-usbsevseg | 5 Description: Controls whether the device's display will powered.
13 Description: Controls the devices display mode.
26 Description: Controls the way the device interprets its text buffer.
27 raw: each character controls its segment manually
41 Description: Controls the decimal places on the device.
|
| 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 …]
|
| 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-hid-lenovo | 4 Description: This controls if mouse clicks should be generated if the trackpoint is quickly pressed…
30 Description: This setting controls if the mouse click events generated by pressing the trackpoint (…
47 Description: This setting controls how fast the trackpoint needs to be pressed to generate a mouse …
56 Description: This setting controls whether Fn Lock is enabled on the keyboard (i.e. if F1 is Mute o…
|
| /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 …]
|
| /Documentation/devicetree/bindings/mux/ |
| D | mux-consumer.yaml | 22 Mux controller properties should be named "mux-controls". The exact meaning of
25 strings to label each of the mux controllers listed in the "mux-controls"
33 Properties "mux-controls" and "mux-states" can be used depending on how
36 "mux-controls" can be used. If the consumer needs to set the mux
46 mux-controls:
56 controller to an index into the list given by the "mux-controls" property.
|
| /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
360 controls 'Standard Signal Mode' and 'Standard' determine what
535 The FM receiver supports RDS as well, both using 'Block I/O' and 'Controls'
536 modes. In the 'Controls' mode the RDS information is stored in read-only
537 controls. These controls are updated every time the frequency is changed,
[all …]
|
| /Documentation/sound/hd-audio/ |
| D | controls.rst | 2 HD-Audio Codec-Specific Mixer Controls
6 This file explains the codec-specific mixer controls.
15 and "8ch". According to the configuration, this also controls the
21 and/or line-out jacks are available on a machine, this controls
56 These enum controls the direction and the bias of the input jack
82 individual volume controls will be no longer available for
115 According to the configuration, this also controls the
|
| /Documentation/devicetree/bindings/net/ |
| D | mdio-mux-multiplexer.yaml | 25 mux-controls:
30 - mux-controls
45 mux-controls = <&mux 0>;
65 mux-controls = <&mux 1>;
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 13 Another is support of stateless codecs, which require controls to be applied
14 to specific frames (aka 'per-frame controls') in order to be used efficiently.
89 Controls can still be set without a request and are applied immediately,
100 associated controls have been updated with the values at the time of completion.
133 to associate specific controls to
136 ability to capture the state of controls when the request completes to read back
139 Put into code, after obtaining a request, user-space can assign controls and one
192 This is particularly useful for volatile controls for which we want to
222 With a simple capture device, requests can be used to specify controls to apply
253 controls and recycle the request as in the M2M example above.
|
| /Documentation/sound/soc/ |
| D | overview.rst | 50 * Machine specific controls: Allow machines to add controls to the sound card
57 contains audio controls, audio interface capabilities, codec DAPM
68 "sound card device". It handles any machine specific controls and
|
| /Documentation/devicetree/bindings/sound/ |
| D | axentia,tse850-pcm5142.txt | 7 - axentia,add-gpios: gpio specifier that controls the mixer.
8 - axentia,loop1-gpios: gpio specifier that controls loop relays on channel 1.
9 - axentia,loop2-gpios: gpio specifier that controls loop relays on channel 2.
32 The 'loop1' gpio pin controls two relays, which are either in loop position,
|
| /Documentation/devicetree/bindings/iio/multiplexer/ |
| D | io-channel-mux.yaml | 34 mux-controls: true
55 - mux-controls
76 mux-controls = <&mux>;
|
| /Documentation/devicetree/bindings/media/ |
| D | video-mux.yaml | 22 mux-controls:
53 - mux-controls
78 mux-controls = <&mux>;
|
12345678910>>...20