| /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"
47 Valid values: 0 - 100 (percent)
61 Valid values: 0 - 100 (percent)
75 Valid values: 0 - 100 (percent)
84 Valid values: "Unknown", "Critical", "Low", "Normal", "High",
96 Valid values: Represented in microamps
105 Valid values: Represented in microamps
[all …]
|
| D | sysfs-platform-chipidea-usb-otg | 13 Valid values are "1" and "0".
28 Valid values are "1" and "0".
43 Valid values are "1" and "0".
56 Valid value is "1"
|
| /Documentation/devicetree/bindings/mmc/ |
| D | sdhci-cadence.txt | 24 They are used to delay the data valid window, and align the window
29 Valid range = [0:0x1F].
32 Valid range = [0:0x1F].
35 Valid range = [0:0x1F].
38 Valid range = [0:0x1F].
41 Valid range = [0:0x1F].
44 Valid range = [0:0x1F].
47 Valid range = [0:0x1F].
50 Valid range = [0:0x1F].
59 Valid range = [0:0x7F].
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,vic.txt | 21 - valid-mask : A one cell big bit mask of valid interrupt sources. Each bit
24 clear means otherwise. If unspecified, defaults to all valid.
25 - valid-wakeup-mask : A one cell big bit mask of interrupt sources that can be
27 valid-mask property. A set bit means that this interrupt source can be
39 valid-mask = <0xffffff7f>;
40 valid-wakeup-mask = <0x0000ff7f>;
|
| /Documentation/hwmon/ |
| D | lochnagar.rst | 31 power1_average_interval Power averaging time input valid from 1 to 1708mS
38 power2_average_interval Power averaging time input valid from 1 to 1708mS
45 power3_average_interval Power averaging time input valid from 1 to 1708mS
52 power4_average_interval Power averaging time input valid from 1 to 1708mS
59 power5_average_interval Power averaging time input valid from 1 to 1708mS
64 power6_average_interval Power averaging time input valid from 1 to 1708mS
71 power7_average_interval Power averaging time input valid from 1 to 1708mS
78 power8_average_interval Power averaging time input valid from 1 to 1708mS
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-mt7622.txt | 40 The following generic properties as defined in pinctrl-bindings.txt are valid
45 Valid values for these names are listed below.
47 group. Valid values for function names are listed below.
51 The following generic properties as defined in pinctrl-bindings.txt are valid
56 Valid values for these names are listed below.
58 Valid values for these names are listed below.
65 Valid arguments for 'slew-rate' are '0' for no slew rate controlled and '1' for
67 Valid arguments for 'drive-strength', 4, 8, 12, or 16 in mA.
69 The following specific properties as defined are valid to specify in a pinconf
74 cycle when asserted (high pulse width adjustment). Valid arguments are from 0
[all …]
|
| D | xlnx,zynq-pinctrl.txt | 34 The following generic properties as defined in pinctrl-bindings.txt are valid
38 The following generic properties as defined in pinctrl-bindings.txt are valid
43 Valid arguments for 'slew-rate' are '0' and '1' to select between slow and fast
46 Valid values for groups are:
58 Valid values for pins are:
61 Valid values for function are:
68 The following driver-specific properties as defined here are valid to specify in
|
| D | nvidia,tegra20-pinmux.txt | 32 group. Valid values for these names are listed below.
36 pin or group. Valid values for function names are listed below. See the Tegra
37 TRM to determine which are valid for each pin or group.
46 - nvidia,low-power-mode: Integer. Valid values 0-3. 0 is least power, 3 is
50 The range of valid values depends on the pingroup. See "CAL_DRVDN" in the
53 The range of valid values depends on the pingroup. See "CAL_DRVUP" in the
56 fastest. The range of valid values depends on the pingroup. See
59 fastest. The range of valid values depends on the pingroup. See
62 Note that many of these properties are only valid for certain specific pins
68 Valid values for pin and group names are:
[all …]
|
| D | pinctrl-mt6797.txt | 44 drive-strength, and slew-rate are valid.
46 Valid arguments for 'slew-rate' are '0' for no slew rate controlled and
47 '1' for slower slew rate respectively. Valid arguments for 'drive-strength'
50 Some optional vendor properties as defined are valid to specify in a
53 duty cycle when asserted (high pulse width adjustment). Valid arguments
56 duty cycle when asserted (high pulse width adjustment). Valid arguments
|
| D | nvidia,tegra194-pinmux.txt | 25 group. Valid values for these names are listed below.
50 - nvidia,drive-type: Integer. Valid range 0...3.
52 The range of valid values depends on the pingroup. See "CAL_DRVDN" in the
55 The range of valid values depends on the pingroup. See "CAL_DRVUP" in the
58 Valid values for pin and group names (nvidia,pin) are:
76 Valid values for nvidia,functions are:
|
| D | lantiq,pinctrl-xway.txt | 42 Valid values for these names are listed below.
44 group. Valid values for function names are listed below.
46 Valid values for group and function names:
135 Valid values for these names are listed below.
142 Valid values for XWAY pin names: (DEPRECATED: Use DANUBE)
145 Valid values for XR9 pin names: (DEPRECATED: Use xrX100/xRX200)
148 Valid values for AMAZON pin names:
151 Valid values for DANUBE pin names:
154 Valid values for xRX100 pin names:
157 Valid values for xRX200 pin names:
[all …]
|
| /Documentation/devicetree/bindings/sram/ |
| D | sunxi-sram.txt | 36 The valid sections compatible for A10 are:
41 The valid sections compatible for A13 are:
46 The valid sections compatible for A20 are:
51 The valid sections compatible for A23/A33 are:
54 The valid sections compatible for H3 are:
57 The valid sections compatible for A64 are:
61 The valid sections compatible for H5 are:
64 The valid sections compatible for H6 are:
68 The valid sections compatible for F1C100s are:
81 This valid values for this argument are:
|
| /Documentation/devicetree/bindings/mfd/ |
| D | max77693.txt | 53 Valid values: 3650000 - 4400000, step by 25000 (rounded down)
57 Valid values: 3000000 - 3700000, step by 100000 (rounded down)
63 Valid values: 70, 85, 100, 115
68 Valid values: 2000000 - 3500000, step by 250000 (rounded down)
75 Valid values: 4300000, 4700000, 4800000, 4900000
99 Valid values: 3300 - 5500, step by 25 (rounded down)
104 Valid values: 2400 - 3400, step by 33 (rounded down)
111 Valid values for a LED connected to one FLED output:
113 Valid values for a LED connected to both FLED outputs:
116 Valid values for a single LED connected to one FLED output
[all …]
|
| D | rk808.txt | 95 - valid values for n are 1 to 4.
97 - valid values for n are 1 to 3
104 - valid values for n are 1 to 4.
106 - valid values for n are 1 to 8.
108 - valid values for n are 1 to 2
115 - valid values for n are 1 to 5 for RK809.
116 - valid values for n are 1 to 4 for RK817.
118 - valid values for n are 1 to 9 for RK809.
119 - valid values for n are 1 to 9 for RK817.
121 - valid values for n are 1 to 2 for RK809.
[all …]
|
| /Documentation/virt/kvm/devices/ |
| D | vm.txt | 122 A subfunction block is only valid if KVM_S390_VM_CPU_MACHINE contains the
130 u8 plo[32]; # always valid (ESA/390 feature)
131 u8 ptff[16]; # valid with TOD-clock steering
132 u8 kmac[16]; # valid with Message-Security-Assist
133 u8 kmc[16]; # valid with Message-Security-Assist
134 u8 km[16]; # valid with Message-Security-Assist
135 u8 kimd[16]; # valid with Message-Security-Assist
136 u8 klmd[16]; # valid with Message-Security-Assist
137 u8 pckmo[16]; # valid with Message-Security-Assist-Extension 3
138 u8 kmctr[16]; # valid with Message-Security-Assist-Extension 4
[all …]
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | brcm,iproc-touchscreen.txt | 18 - scanning_period: Time between scans. Each step is 1024 us. Valid 1-256.
19 - debounce_timeout: Each step is 512 us. Valid 0-255
23 Valid values: 0-11
38 Valid values 0-255.
41 Valid values 0-7
52 Valid values 0-31
|
| /Documentation/devicetree/bindings/bus/ |
| D | qcom,ebi2.txt | 9 data lines (16 bits), OE (output enable), ADV (address valid, used on some
36 in the hardware, or what valid values exist. The current hypothesis is that
80 CS or read followed by write on the same CS. Valid values 0 thru 15. Minimum
85 stays active for 1 extra cycle etc. Valid values 0 thru 15.
87 the first write to a page or burst memory. Valid values 0 thru 255.
89 first read to a page or burst memory. Valid values 0 thru 255.
91 cycle. Valid values 0 thru 15.
93 cycle. Valid values 0 thru 15.
100 assertion, with respect to the cycle where ADV (address valid) is asserted.
101 2 means 2 cycles between ADV and OE. Valid values 0, 1, 2 or 3.
[all …]
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | tps65217-backlight.txt | 10 - isel: selection bit, valid values: 1 for ISEL1 (low-level) and 2 for ISEL2 (high-level)
11 - fdim: PWM dimming frequency, valid values: 100, 200, 500, 1000
12 - default-brightness: valid values: 0-100
|
| /Documentation/devicetree/bindings/input/ |
| D | microchip,qt1050.txt | 26 - reg: The key number. Valid values: 0, 1, 2, 3, 4.
36 Valid value range: 0 - 637500; values must be a multiple of 2500;
40 Valid values: 1, 4, 16, 64, 256, 1024, 4096, 16384; default is 1.
43 Valid values: 1, 2, 4, 8, 16, 32, 64, 128; default is 1.
46 Valid value range: 0 - 255; default is 20.
|
| /Documentation/devicetree/bindings/iio/dac/ |
| D | ad5755.txt | 24 Valid values for DC DC Phase control is:
33 Valid values for DC DC frequency is [Hz]:
38 Valid values for the maximum allowed Vboost voltage supplied by
47 Valid values for DAC modes is:
61 Valid values for the slew rate update frequency:
79 Valid values for the step size LSBs:
|
| /Documentation/media/uapi/dvb/ |
| D | frontend-property-satellite-systems.rst | 22 The following parameters are valid for DVB-S:
45 are also valid.
59 In addition to all parameters valid for DVB-S, DVB-S2 supports the
73 are also valid.
81 In addition to all parameters valid for DVB-S, turbo code supports the
92 The following parameters are valid for ISDB-S:
|
| D | frontend-property-terrestrial-systems.rst | 22 The following parameters are valid for DVB-T:
53 are also valid.
64 The following parameters are valid for DVB-T2:
97 are also valid.
129 The following parameters are valid for ISDB-T:
186 are also valid.
194 The following parameters are valid for ATSC:
211 are also valid.
219 The following parameters are valid for ATSC-MH:
264 are also valid.
[all …]
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | divider.txt | 17 ti,index-starts-at-one - valid divisor values start at 1, not the default
24 ti,index-power-of-two - valid divisor values are powers of two. E.g:
30 Additionally an array of valid dividers may be supplied like so:
69 - ti,index-starts-at-one : valid divisor programming starts at 1, not zero,
70 only valid if ti,dividers is not defined.
71 - ti,index-power-of-two : valid divisor programming must be a power of two,
72 only valid if ti,dividers is not defined.
|
| /Documentation/media/uapi/v4l/ |
| D | v4l2-selection-targets.rst | 31 - Valid for V4L2
32 - Valid for V4L2 subdev
45 - Bounds of the crop rectangle. All valid crop rectangles fit inside
67 - Bounds of the compose rectangle. All valid compose rectangles fit
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | qcom,spmi-vadc.txt | 66 - For compatible property "qcom,spmi-vadc", valid values are
69 - For compatible property "qcom,spmi-adc5", valid values are 250, 420
71 - For compatible property "qcom,spmi-adc-rev2", valid values are 256,
103 conversion. The 'hw_settle_time' is an index used from valid values
108 Valid values are: 0, 100, 200, 300, 400, 500, 600, 700, 800,
114 Valid values are: 15, 100, 200, 300, 400, 500, 600, 700, 800,
116 Certain controller digital versions have valid values of
127 - For compatible property "qcom,spmi-vadc", valid values
131 valid values are: 1, 2, 4, 8, 16
|