Searched full:values (Results 1 – 25 of 1468) sorted by relevance
12345678910>>...59
| /Documentation/userspace-api/gpio/ |
| D | gpio-handle-get-line-values-ioctl.rst | 10 gpio-v2-line-get-values-ioctl.rst.
15 GPIOHANDLE_GET_LINE_VALUES_IOCTL - Get the values of all requested lines.
22 ``int ioctl(int handle_fd, GPIOHANDLE_GET_LINE_VALUES_IOCTL, struct gpiohandle_data *values)``
31 ``values``
37 Get the values of all requested lines.
39 The values returned are logical, indicating if the line is active or inactive.
41 values (high/low) and logical values (active/inactive).
46 The values of both input and output lines may be read.
55 one line requested in that case, only the one value is returned in ``values``.
60 On success 0 and ``values`` populated with the values read.
|
| D | gpio-handle-set-line-values-ioctl.rst | 10 gpio-v2-line-set-values-ioctl.rst.
15 GPIO_HANDLE_SET_LINE_VALUES_IOCTL - Set the values of all requested output lines.
22 ``int ioctl(int handle_fd, GPIO_HANDLE_SET_LINE_VALUES_IOCTL, struct gpiohandle_data *values)``
31 ``values``
37 Set the values of all requested output lines.
39 The values set are logical, indicating if the line is to be active or inactive.
41 values (active/inactive) and physical values (high/low).
46 Only the values of output lines may be set.
|
| D | gpio-v2-line-get-values-ioctl.rst | 12 GPIO_V2_LINE_GET_VALUES_IOCTL - Get the values of requested lines.
19 ``int ioctl(int req_fd, GPIO_V2_LINE_GET_VALUES_IOCTL, struct gpio_v2_line_values *values)``
28 ``values``
35 Get the values of requested lines.
37 The values returned are logical, indicating if the line is active or inactive.
39 values (high/low) and logical values (active/inactive).
44 The values of both input and output lines may be read.
54 On success 0 and the corresponding :c:type:`values.bits<gpio_v2_line_values>`
|
| D | gpio-v2-line-set-values-ioctl.rst | 12 GPIO_V2_LINE_SET_VALUES_IOCTL - Set the values of requested output lines.
19 ``int ioctl(int req_fd, GPIO_V2_LINE_SET_VALUES_IOCTL, struct gpio_v2_line_values *values)``
28 ``values``
36 Set the values of requested output lines.
38 The values set are logical, indicating if the line is to be active or inactive.
40 values (active/inactive) and physical values (high/low).
45 Only the values of output lines may be set.
|
| /Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | 10 Values: 64 bit unsigned integer (bit field)
25 Values: 64 bit unsigned integer (bit field)
31 Values: integer
37 Values: integer
43 Values: integer
49 Values: integer
55 Values: integer
61 Values: integer
66 Values: hexadecimal bitmask.
72 Values: decimal list.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-power | 10 Valid values: Represented as string
19 Valid values: Represented as string
28 Valid values: Represented as string
37 Valid values: "Battery", "UPS", "Mains", "USB", "Wireless"
60 Valid values: Represented in microamps. Negative values are
61 used for discharging batteries, positive values for charging
77 Valid values: Represented in microamps
100 Valid values: Represented in microamps. Negative values are
101 used for discharging batteries, positive values for charging
120 Valid values: Represented in 1/10 Degrees Celsius
[all …]
|
| D | sysfs-tty | 29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
104 These sysfs values expose the TIOCGSERIAL interface via
113 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| D | sysfs-class-switchtec | 20 Values: arbitrary string.
28 Values: integer.
37 Values: arbitrary string.
45 Values: integer.
53 Values: integer (in hexadecimal).
61 Values: integer.
69 Values: integer.
78 Values: arbitrary string.
87 Values: arbitrary string.
96 Values: arbitrary string.
|
| D | sysfs-class-power-ltc4162l | 9 Valid values:
27 Valid values: Signed value in microamps
37 Valid values: In microvolts
47 Valid values: In microvolts
63 Valid values: 0 (disabled) or 1 (enabled)
82 Valid values: 0 (disable) or 1 (enable)
|
| D | sysfs-driver-hid-wiimote | 57 values for all 4 sensors. The values are separated by colons and
59 First, 0kg values for all 4 sensors are written, followed by the
60 17kg values for all 4 sensors and last the 34kg values for all 4
64 values but may be used by user-space to perform other
73 values for all 4 analog sticks. Format is: "x1:y1 x2:y2". Data
79 values but may be used by user-space to perform other
85 set the calibration values manually.
|
| D | sysfs-driver-ccp | 18 Possible values:
29 Possible values:
40 Possible values:
51 Possible values:
63 Possible values:
74 Possible values:
85 Possible values:
|
| D | sysfs-driver-toshiba_acpi | 6 values are:
26 valid values range from 0-60.
45 stick (if available), valid values are:
92 values, kernel 4.0 only supports the first three.
104 values can be:
109 Currently it prints two values, the first one indicates if the
133 Description: This file controls the Sleep & Music state, which values can be:
155 values are:
165 mode, valid values are:
183 the LID is opened, valid values are:
[all …]
|
| /Documentation/hwmon/ |
| D | lm95245.rst | 33 All temperature values are given in millidegrees Celsius. Local temperature
40 user-space applications, two absolute values are exported, one for each
41 channel, but these values are of course linked. Only the local hysteresis
45 The lm95245 driver can change its update interval to a fixed set of values.
47 values. Reading sensor values more often will do no harm, but will return
48 'old' values.
|
| D | lm95234.rst | 36 All temperature values are given in millidegrees Celsius. Temperature
45 The lm95234 driver can change its update interval to a fixed set of values.
47 values. Reading sensor values more often will do no harm, but will return
48 'old' values.
|
| /Documentation/devicetree/bindings/powerpc/opal/ |
| D | power-mgt.txt | 41 Array of unsigned 32-bit values containing the values of the
61 Array of unsigned 32-bit values containing the values of the
66 Array of unsigned 32-bit values containing the values of the
74 Array of unsigned 64-bit values containing the values for the
79 Array of unsigned 64-bit values containing the masks
90 values.
101 For all the other values of the entry in
107 Array of unsigned 64-bit values containing the pmicr values
115 Array of unsigned 64-bit values containing the mask indicating
|
| /Documentation/misc-devices/ |
| D | apds990x.rst | 23 ALS produces raw measurement values for two channels: Clear channel
29 only lux values. Lux value is calculated using information from the both
38 Platform data can provide tuned values to the conversion formulas if
39 values are known. Otherwise plain sensor default values are used.
42 It produces directly usable values.
118 values: 0 or prox0_sensor_range value. 0 means no proximity,
120 In "periodic" mode the driver reports all values above
125 RO - accepted values to prox0_reporting_mode (trigger, periodic)
|
| /Documentation/devicetree/bindings/sound/ |
| D | wlf,arizona.yaml | 30 A list of INn_MODE register values, where n is the number of input
31 signals. Valid values are 0 (Differential), 1 (Single-ended) and
33 default. If present, values must be specified less than or equal
34 to the number of input signals. If values less than the number of
48 A list of boolean values indicating whether each output is mono
51 value indicates a mono output. If present, the number of values
52 should be less than or equal to the number of outputs, if less values
67 of values should be less than or equal to the number of inputs,
95 the datasheet for values. The second cell is ignored for codecs that
104 the datasheet for values. The second cell is ignored for codecs that
[all …]
|
| /Documentation/trace/coresight/ |
| D | coresight-config.rst | 33 is device dependent, and can be defined in terms of absolute register values,
34 resource usage and parameter values.
66 Users can update parameter values using the configfs API for the CoreSight
87 as well as any preset values that can be used to override default parameter
88 values.
91 Preset Values
94 Preset values are easily selectable sets of parameter values for the features
95 that the configuration uses. The number of values in a single preset set, equals
96 the sum of parameter values in the features used by the configuration.
100 therefore have 3 values.
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | maxim,max77693.yaml | 41 Valid values: 3300 - 5500, step by 25 (rounded down)
52 Valid values: 2400 - 3400, step by 33 (rounded down)
75 Valid values for a LED connected to one FLED output:
77 Valid values for a LED connected to both FLED outputs:
82 Valid values for a single LED connected to one FLED output
85 Valid values for a single LED connected to both FLED outputs:
87 Valid values for two LEDs case:
92 Valid values: 62500 - 1000000, step by 62500 (rounded down)
|
| /Documentation/input/devices/ |
| D | walkera0701.rst | 46 cable and run jstest /dev/input/js0 to see values from TX. If no value can
85 Binary values: Analog octal values:
96 24 bin+oct values + 1 bin value = 24*4+1 bits = 97 bits
105 values can be sampled between sync pulses.
107 Values for first four channels (analog joystick values) can be found in
125 Summary of octal values in nibbles must be same as octal value in checksum
127 calculated by sum of binary values in checked nibbles + sum of octal values
|
| /Documentation/virt/kvm/arm/ |
| D | vcpu-features.rst | 27 system. The ID register values may be VM-scoped in KVM, meaning that the
28 values could be shared for all vCPUs in a VM.
31 registers by writing values to them via the ``KVM_SET_ONE_REG`` ioctl. The ID
40 scheme for fields in ID register'. KVM does not allow ID register values that
44 It is **strongly recommended** that userspace modify the ID register values
46 ID register values to control feature emulation. Interleaving ID register
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe_property_parameters.rst | 121 Possible values: ``1712000``, ``5000000``, ``6000000``, ``7000000``,
125 Terrestrial Standard Possible values for bandwidth
164 The acceptable values are defined by :c:type:`fe_spectral_inversion`.
192 The acceptable values are defined by :c:type:`fe_code_rate`.
207 The acceptable values are defined by :c:type:`fe_sec_voltage`.
227 The acceptable values are defined by :c:type:`fe_pilot`.
239 The acceptable values are defined by :c:type:`fe_rolloff`.
273 The acceptable values are defined by :c:type:`fe_delivery_system`.
286 If '1' ``DTV_ISDBT_LAYERA_*`` values are assigned to the center segment
293 Possible values: 0, 1, -1 (AUTO)
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | stericsson,u8500-clks.yaml | 52 which PRCC block the consumer wants to use, possible values are 1, 2, 3,
54 wants, possible values are 0 thru 31.
66 block the consumer wants to use, possible values are 1, 2, 3, 5, 6. The
68 values are 0 thru 31.
80 which PRCC block the consumer wants to use, possible values are 1, 2, 3
82 it wants to control, possible values are 0 thru 31.
122 possible values are 0 (CLKOUT1) and 1 (CLKOUT2).
124 possible values are 0 thru 7, see the defines for the different
126 The third cell is a divider, legal values are 1 thru 63.
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 13 # * What values are possible for CORE?
15 # CORE_BELL_A_ADVANCED selects CORE, which means that it influences the values
30 # what values are possible for CORE we ended up needing to address questions
31 # regarding possible values of CORE itself again. Answering the original
32 # question of what are the possible values of CORE would make the kconfig
|
| /Documentation/devicetree/bindings/phy/ |
| D | qcom,usb-snps-femto-v2.yaml | 68 The hardware accepts only discrete values. The value closest to the
77 The hardware accepts only discrete values. The value closest to the
85 The hardware accepts only discrete values. The value closest to the
97 The hardware accepts only discrete values. The value closest to the
109 The hardware accepts only discrete values. The value closest to the
117 The hardware accepts only discrete values. The value closest to the
126 The hardware accepts only discrete values. The value closest to the
136 resistance on the USB. The hardware accepts only discrete values. The
145 impedance while driving high. The following adjustment values are based
147 The hardware accepts only discrete values. The value closest to the
|
12345678910>>...59