Searched full:valid (Results 1 – 25 of 885) sorted by relevance
12345678910>>...36
| /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
77 Valid values: Represented in microamps
100 Valid values: Represented in microamps. Negative values are
120 Valid values: Represented in 1/10 Degrees Celsius
144 Valid values: Represented in 1/10 Degrees Celsius
169 Valid values: Represented in 1/10 Degrees Celsius
[all …]
|
| 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-input-exc3000 | 8 Valid values: Represented as string
17 Valid values: Represented as string
26 Valid values: Represented as string
|
| D | sysfs-class-power-mp2629 | 9 Valid values: Represented in milli-ohms. Valid range is [0, 140].
|
| 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/userspace-api/media/v4l/ |
| D | vidioc-g-ext-ctrls.rst | 62 set ``size`` to a valid value and return an ``ENOSPC`` error code. You
79 control values are valid.
86 values are automatically adjusted to a valid value or if an error is
91 closest valid value or return an ``ERANGE`` error code, whatever seems more
164 - New value or current value. Valid if this control is not of type
169 - New value or current value. Valid if this control is of type
174 - A pointer to a string. Valid if this control is of type
178 - A pointer to a matrix control of unsigned 8-bit values. Valid if
182 - A pointer to a matrix control of unsigned 16-bit values. Valid if
186 - A pointer to a matrix control of unsigned 32-bit values. Valid if
[all …]
|
| D | v4l2-selection-targets.rst | 30 - Valid for V4L2
31 - Valid for V4L2 subdev
46 - Bounds of the crop rectangle. All valid crop rectangles fit inside
68 - Bounds of the compose rectangle. All valid compose rectangles fit
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,vic.yaml | 42 valid-mask:
44 A one cell big bit mask of valid interrupt sources. Each bit
48 defaults to all valid.
51 valid-wakeup-mask:
55 valid-mask property. A set bit means that this interrupt source
77 valid-mask = <0xffffff7f>;
78 valid-wakeup-mask = <0x0000ff7f>;
|
| /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/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/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 …]
|
| D | nvidia,tegra20-gmi.txt | 57 bus. Valid values are 0-15, default is 1
60 (in case of MASTER Request). Valid values are 0-15, default is 1
62 Valid values are 0-15, default is 1.
64 Valid values are 0-15, default is 4
66 Valid values are 0-15, default is 1
68 Valid values are 0-255, default is 1
70 Valid values are 0-255, default is 3
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend-property-satellite-systems.rst | 15 The following parameters are valid for DVB-S:
38 are also valid.
52 In addition to all parameters valid for DVB-S, DVB-S2 supports the
66 are also valid.
74 In addition to all parameters valid for DVB-S, turbo code supports the
85 The following parameters are valid for ISDB-S:
|
| D | frontend-property-terrestrial-systems.rst | 15 The following parameters are valid for DVB-T:
46 are also valid.
57 The following parameters are valid for DVB-T2:
90 are also valid.
122 The following parameters are valid for ISDB-T:
179 are also valid.
187 The following parameters are valid for ATSC:
204 are also valid.
212 The following parameters are valid for ATSC-MH:
257 are also valid.
[all …]
|
| D | frontend-property-cable-systems.rst | 22 The following parameters are valid for DVB-C Annex A/C:
45 are also valid.
56 The following parameters are valid for DVB-C Annex B:
75 are also valid.
|
| /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.
|
| D | dlg,da7280.txt | 31 Valid values: 0 - 6000000.
33 Valid values: 0 - 6000000.
35 Valid values: 0 - 252000.
38 Valid values: 0 - 1500000000.
49 Valid range: 0 - 15.
52 Valid range: 0 - 15.
55 Valid range: 0 - 15.
|
| /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/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra-pinmux-common.yaml | 38 Note that many of these properties are only valid for certain specific pins
48 or group. Valid values for these names are listed below.
53 pin or group. Valid values for function names are listed below. See the
54 Tegra TRM to determine which are valid for each pin or group.
86 description: Controls drive strength. 0 is weakest. The range of valid
91 description: Controls drive strength. 0 is weakest. The range of valid
105 description: Controls the drive power or current. Valid values are from 0
169 valid values depends on the pingroup. See "DRVDN_SLWR" in the Tegra TRM.
174 valid values depends on the pingroup. See "DRVUP_SLWF" in the Tegra TRM.
|
| D | lantiq,pinctrl-xway.txt | 38 Valid values for these names are listed below.
40 group. Valid values for function names are listed below.
42 Valid values for group and function names:
108 Valid values for these names are listed below.
115 Valid values for AMAZON pin names:
118 Valid values for DANUBE pin names:
121 Valid values for xRX100 pin names:
124 Valid values for xRX200 pin names:
127 Valid values for xRX300 pin names:
|
| D | qcom,apq8084-pinctrl.txt | 77 The following generic properties as defined in pinctrl-bindings.txt are valid
84 this subnode. Valid pins are:
97 specified pins. Functions are only valid for gpio pins.
98 Valid values are:
142 Not valid for sdc pins.
149 Not valid for sdc pins.
155 Valid values are: 2, 4, 6, 8, 10, 12, 14 and 16
|
| /Documentation/devicetree/bindings/phy/ |
| D | samsung,mipi-video-phy.yaml | 40 Phandle to PMU system controller interface, valid only for
48 Phandle to PMU system controller interface, valid for
54 Phandle to DISP system controller interface, valid for
60 Phandle to CAM0 system controller interface, valid for
66 Phandle to CAM1 system controller interface, valid for
|
| /Documentation/networking/device_drivers/cellular/qualcomm/ |
| D | rmnet.rst | 88 Function Reserved Valid Checksum start offset
95 Valid bit indicates whether the partial checksum is calculated and is valid.
96 Set to 1, if its is valid. Set to 0 otherwise.
141 Function Header Type Next Header Checksum Valid Reserved
151 Checksum Valid is to indicate whether the header checksum is valid. Value of 1
152 implies that checksum is calculated on this packet and is valid, value of 0
|
12345678910>>...36