Searched full:control (Results 1 – 25 of 1943) sorted by relevance
12345678910>>...78
| /Documentation/userspace-api/media/drivers/ |
| D | uvcvideo.rst | 28 control enumeration.
37 Control mappings
41 control mappings at runtime. These allow for individual XU controls or byte
45 triggers a read or write of the associated XU control.
47 The ioctl used to create these control mappings is called UVCIOC_CTRL_MAP.
49 beforehand (UVCIOC_CTRL_ADD) to pass XU control information to the UVC driver.
57 3. Driver specific XU control interface
65 directly map to the low-level UVC control requests.
67 In order to make such a request the UVC unit ID of the control's extension unit
68 and the control selector need to be known. This information either needs to be
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | extended-controls.rst | 13 The control mechanism as originally designed was meant to be used for
19 implementing this extended control mechanism: the MPEG standard is quite
27 Unfortunately, the original control API lacked some features needed for
29 named) extended control API.
32 Extended Control API, nowadays there are also other classes of Extended
38 The Extended Control API
48 control). This is needed since it is often required to atomically change
53 contains a pointer to the control array, a count of the number of
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
[all …]
|
| D | vidioc-g-ext-ctrls.rst | 13 …C_S_EXT_CTRLS - VIDIOC_TRY_EXT_CTRLS - Get or set the value of several controls, try control values
43 atomically. Control IDs are grouped into control classes (see
44 :ref:`ctrl-class`) and all controls in the control array must belong
45 to the same control class.
60 If the ``size`` is too small to receive the control result (only
79 control values are valid.
93 :c:type:`v4l2_ext_control`. If the new control value
95 control), then this will also result in an ``EINVAL`` error code error.
116 The driver will only set/get these controls if all control values are
138 - Identifies the control, set by the application.
[all …]
|
| D | vidioc-queryctrl.rst | 13 VIDIOC_QUERYCTRL - VIDIOC_QUERY_EXT_CTRL - VIDIOC_QUERYMENU - Enumerate controls and menu control i…
41 To query the attributes of a control applications set the ``id`` field
49 exclusive ``V4L2_CID_LASTP1``. Drivers may return ``EINVAL`` if a control in
56 in the ``flags`` field this control is permanently disabled and should
60 driver returns the next supported non-compound control, or ``EINVAL`` if
63 type ≥ ``V4L2_CTRL_COMPOUND_TYPES`` and/or array control, in other words
71 control information that cannot be returned in struct
95 See also the examples in :ref:`control`.
110 - Identifies the control, set by the application. See
111 :ref:`control-id` for predefined IDs. When the ID is ORed with
[all …]
|
| D | vidioc-g-ctrl.rst | 13 VIDIOC_G_CTRL - VIDIOC_S_CTRL - Get or set the value of a control
38 To get the current value of a control applications initialize the ``id``
41 value of a control applications initialize the ``id`` and ``value``
49 actual new value. If the ``value`` is inappropriate for the control
50 (e.g. if it refers to an unsupported menu index of a menu control), then
53 These ioctls work only with user controls. For other control classes the
69 - Identifies the control, set by the application.
83 or the ``value`` is inappropriate for the given control (i.e. if a
92 The control is temporarily not changeable, possibly because another
93 applications took over control of the device function this control
[all …]
|
| D | control.rst | 14 control ioctls provide the information and a mechanism to create a nice
21 pre-defined control IDs have the prefix ``V4L2_CID_``, and are listed in
22 :ref:`control-id`. The ID is used when querying the attributes of a
23 control, and when getting or setting the current value.
26 assumptions about their purpose. Each control comes with a name string
36 value, step size or other menu items. A control with a certain *custom*
39 If a control is not applicable to the current configuration of the
43 Control values are stored globally, they do not change when switching
52 in order to always reflect the correct control value.
59 Control IDs
[all …]
|
| D | ext-ctrls-image-process.rst | 6 Image Process Control Reference
9 The Image Process control class is intended for low-level control of
11 controls in this class affect processing the image, and do not control
15 .. _image-process-control-id:
17 Image Process Control IDs
31 Pixel sampling rate in the device's pixel array. This control is
37 control may be present in a different sub-device than the blanking controls
41 horizontal and vertical blanking. The unit of this control is Hz.
55 control value divided by e.g. 0x100, meaning that to get no
56 digital gain the control value needs to be 0x100. The no-gain
|
| D | ext-ctrls-jpeg.rst | 6 JPEG Control Reference
15 .. _jpeg-control-id:
17 JPEG Control IDs
22 :ref:`VIDIOC_QUERYCTRL` for this control will
23 return a description of this control class.
29 details. The ``V4L2_CID_JPEG_CHROMA_SUBSAMPLING`` control determines
61 ``V4L2_CID_JPEG_RESTART_INTERVAL`` control is set to 0, DRI and RSTm
64 .. _jpeg-quality-control:
68 It provides simpler method for applications to control image quality,
72 elsewhere, ``V4L2_CID_JPEG_COMPRESSION_QUALITY`` control should be set by
[all …]
|
| D | ext-ctrls-image-source.rst | 6 Image Source Control Reference
9 The Image Source control class is intended for low-level control of
15 .. _image-source-control-id:
17 Image Source Control IDs
27 the pixel rate defined by ``V4L2_CID_PIXEL_RATE`` control in the
53 This control returns the unit cell size in nanometers. The struct
56 This control does not take into consideration any possible hardware
60 This control is required for automatic calibration of sensors/cameras.
84 control taking 4 gain values, being the gains for each of the
88 The use of an array allows this control to be extended to sensors
|
| D | ext-ctrls-camera.rst | 6 Camera Control Reference
13 .. _camera-control-id:
15 Camera Control IDs
20 :ref:`VIDIOC_QUERYCTRL` for this control will
21 return a description of this control class.
60 ``APERTURE_PRIORITY``, this control determines if the device may
66 when ``V4L2_CID_EXPOSURE_AUTO`` control is set to ``AUTO``,
108 This control turns the camera horizontally by the specified amount.
112 control.
115 This control turns the camera vertically by the specified amount.
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | micrel-ksz90x1.txt | 14 All skew control options are specified in picoseconds. The minimum
48 - rxc-skew-ps : Skew control of RXC pad
49 - rxdv-skew-ps : Skew control of RX CTL pad
50 - txc-skew-ps : Skew control of TXC pad
51 - txen-skew-ps : Skew control of TX CTL pad
52 - rxd0-skew-ps : Skew control of RX data 0 pad
53 - rxd1-skew-ps : Skew control of RX data 1 pad
54 - rxd2-skew-ps : Skew control of RX data 2 pad
55 - rxd3-skew-ps : Skew control of RX data 3 pad
56 - txd0-skew-ps : Skew control of TX data 0 pad
[all …]
|
| /Documentation/driver-api/media/ |
| D | v4l2-controls.rst | 9 The V4L2 control API seems simple enough, but quickly becomes very hard to
15 1) How do I add a control?
16 2) How do I set the control's value? (i.e. s_ctrl)
20 3) How do I get the control's value? (i.e. g_volatile_ctrl)
21 4) How do I validate the user's proposed control value? (i.e. try_ctrl)
25 The control framework was created in order to implement all the rules of the
29 Note that the control framework relies on the presence of a struct
39 The :c:type:`v4l2_ctrl` object describes the control properties and keeps
40 track of the control's value (both the current value and the proposed new
93 1.3) Hook the control handler into the driver:
[all …]
|
| /Documentation/devicetree/bindings/sram/ |
| D | allwinner,sun4i-a10-system-control.yaml | 4 $id: http://devicetree.org/schemas/sram/allwinner,sun4i-a10-system-control.yaml#
7 title: Allwinner A10 System Control
32 - allwinner,sun4i-a10-system-control
33 - allwinner,sun5i-a13-system-control
34 - allwinner,sun8i-a23-system-control
35 - allwinner,sun8i-h3-system-control
36 - allwinner,sun20i-d1-system-control
37 - allwinner,sun50i-a64-system-control
38 - allwinner,sun50i-h5-system-control
39 - allwinner,sun50i-h616-system-control
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-usb-gadget-uac2 | 14 c_mute_present capture mute control enable
15 c_volume_present capture volume control enable
16 c_volume_min capture volume control min value
18 c_volume_max capture volume control max value
20 c_volume_res capture volume control resolution
27 p_mute_present playback mute control enable
28 p_volume_present playback volume control enable
29 p_volume_min playback volume control min value
31 p_volume_max playback volume control max value
33 p_volume_res playback volume control resolution
[all …]
|
| D | configfs-usb-gadget-uac1 | 11 c_mute_present capture mute control enable
12 c_volume_present capture volume control enable
13 c_volume_min capture volume control min value
15 c_volume_max capture volume control max value
17 c_volume_res capture volume control resolution
22 p_mute_present playback mute control enable
23 p_volume_present playback volume control enable
24 p_volume_min playback volume control min value
26 p_volume_max playback volume control max value
28 p_volume_res playback volume control resolution
|
| D | sysfs-platform-asus-laptop | 24 Control the gps device. 1 means on, 0 means off.
34 To control the LED display, use the following::
38 where T control the 3 letters display, and DDD the 3 digits display.
46 Control the bluetooth device. 1 means on, 0 means off.
47 This may control the led, the device or both.
55 Control the wlan device. 1 means on, 0 means off.
56 This may control the led, the device or both.
64 Control the wimax device. 1 means on, 0 means off.
71 Control the wwan (3G) device. 1 means on, 0 means off.
|
| /Documentation/devicetree/bindings/phy/ |
| D | ti-phy.txt | 3 OMAP CONTROL PHY
7 "ti,control-phy-otghs" - if it has otghs_control mailbox register as on OMAP4.
8 "ti,control-phy-usb2" - if it has Power down bit in control_dev_conf register
10 "ti,control-phy-pipe3" - if it has DPLL and individual Rx & Tx power control
12 "ti,control-phy-pcie" - for pcie to support external clock for pcie and to
15 "ti,control-phy-usb2-dra7" - if it has power down register like USB2 PHY on
17 "ti,control-phy-usb2-am437" - if it has power down register like USB2 PHY on
20 - reg-names: "otghs_control" for control-phy-otghs
21 "power", "pcie_pcs" and "control_sma" for control-phy-pcie
24 omap_control_usb: omap-control-usb@4a002300 {
[all …]
|
| /Documentation/sound/cards/ |
| D | img-spdif-in.rst | 10 This control returns a mask that shows which of the IEC958 status bits
11 can be read using the 'IEC958 Capture Default' control.
15 This control returns the status bits contained within the SPDIF stream that
17 from this control.
24 This control is used to attempt acquisition of up to four different sample
26 control.
28 When the value of this control is set to {0,0,0,0}, the rate given to hw_params
38 This control returns the active capture rate, or 0 if a lock has not been
43 This control is used to modify the locking/jitter rejection characteristics
49 This control is used to change the threshold at which a lock is acquired.
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | syna.txt | 32 * Marvell Berlin CPU control bindings
34 CPU control register allows various operations on CPUs, like resetting them
48 * Marvell Berlin2 chip control binding
50 Marvell Berlin SoCs have a chip control register set providing several
53 chip control registers, so there should be a single DT node only providing the
61 BG2/BG2CD: chip control register set
62 BG2Q: chip control register set and cpu pll registers
64 * Marvell Berlin2 system control binding
66 Marvell Berlin SoCs have a system control register set providing several
73 - reg: address and length of the system control register set
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-trap.rst | 58 | Non-control traps
96 entry) and trapped to the control plane for resolution. Packets are
98 action of such traps is not allowed, as it can easily break the control
100 * ``control``: Trapped packets were trapped by the device because these are
101 control packets required for the correct functioning of the control plane.
105 the control plane.
256 - ``control``
259 - ``control``
262 - ``control``
265 - ``control``
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | nvidia,tegra124-dfll.txt | 9 control module that will automatically adjust the VDD_CPU voltage by
17 - registers for the DFLL control logic.
25 - soc: Clock source for the DFLL control logic.
31 - dvco: Reset control for the DFLL DVCO.
36 the I2C register, control values and supported voltages.
38 Required properties for the control loop parameters:
39 - nvidia,sample-rate: Sample rate of the DFLL control loop.
46 Optional properties for the control loop parameters:
50 - nvidia,pwm-to-pmic: Use PWM to control regulator rather then I2C.
58 control is disabled and the PWM output is tristated. Note that this voltage is
[all …]
|
| /Documentation/driver-api/ |
| D | reset.rst | 10 Reset controllers are central units that control the reset signals to multiple
14 <#reset-consumer-api>`__), which allows peripheral drivers to request control
34 Reset control
36 Control method that determines the state of one or multiple reset lines.
38 either allows direct control over the physical state of the reset line, or
46 A hardware module that provides a number of reset controls to control a
64 reset inputs, which are mapped to an actual reset control on an existing reset
74 assertion or direct, exclusive control.
76 the reset control is requested, either via devm_reset_control_get_shared() or
79 control.
[all …]
|
| /Documentation/devicetree/bindings/thermal/ |
| D | armada-thermal.txt | 21 to the status register (4B). The second one points to the control
25 "control MSB/control 1", with size of 4 (deprecated binding), or point
26 to "control LSB/control 0" with size of 8 (current binding). All other
27 compatibles must point to "control LSB/control 0" with size of 8.
|
| /Documentation/devicetree/bindings/sound/ |
| D | audio-iio-aux.yaml | 31 snd-control-invert-range:
40 Invert the sound control value compared to the IIO channel raw value.
41 - 1: The related sound control value is inverted meaning that the
42 minimum sound control value correspond to the maximum IIO channel
43 raw value and the maximum sound control value correspond to the
45 - 0: The related sound control value is not inverted meaning that the
46 minimum (resp maximum) sound control value correspond to the
63 snd-control-invert-range = <0 1 1 0>;
|
| /Documentation/sound/soc/ |
| D | codec.rst | 14 2. Codec control IO - using RegMap API
22 7. DAC Digital mute control.
67 Codec control IO
70 (AC97 combines control with data in the DAI). The codec driver should use the
83 Defines a single control as follows:-
86 xname = Control name e.g. "Playback Volume"
88 shift = control bit(s) offset in register
89 mask = control bit size(s) e.g. mask of 7 = 3 bits
90 invert = the control is inverted
97 A stereo control
[all …]
|
12345678910>>...78