Searched full:initial (Results 1 – 25 of 369) sorted by relevance
12345678910>>...15
| /Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 35 initial returning value. When the AML tables implement this control method
36 with cached value, the initial returning value is likely not reliable.
37 There are platforms always return "closed" as initial lid state.
71 events and the unreliable initial state notification, Linux users can use
76 initial lid state using the returning value of the _LID control method
81 of the _LID control method is reliable but the initial lid state
89 initial lid state as "opened" and whether the "opened"/"closed" events
93 control method is not reliable and the initial lid state notification is
97 and the unreliable initial state notification, Linux users should always
102 initial lid state and there is a compensation mechanism implemented to
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb4604.txt | 10 - initial-mode: Should specify initial mode.
18 initial-mode = <1>;
|
| D | smsc,usb3503.yaml | 54 initial-mode:
57 Specifies initial mode. 1 for Hub mode, 2 for standby mode and 3 for bypass mode.
98 initial-mode:
102 initial-mode:
120 initial-mode = <1>;
139 initial-mode = <3>;
151 initial-mode = <1>; /* initialize in HUB mode */
|
| /Documentation/devicetree/bindings/regulator/ |
| D | rohm,bd96801-regulator.yaml | 31 rohm,initial-voltage-microvolt:
33 Initial voltage for regulator. Voltage can be tuned +/-150 mV from
48 rohm,initial-voltage-microvolt:
50 Initial voltage for regulator. Voltage can be tuned +/-150 mV from
|
| D | maxim,max77802.yaml | 23 Certain regulators support "regulator-initial-mode" and "regulator-mode".
43 LDOs supporting the regulator-initial-mode property and changing their
56 regulator-initial-mode: false
68 regulator-initial-mode: false
77 regulator-initial-mode: false
|
| D | microchip,mcp16502.yaml | 58 regulator-initial-mode:
61 description: Initial operating mode
97 regulator-initial-mode = <2>;
116 regulator-initial-mode = <2>;
135 regulator-initial-mode = <2>;
154 regulator-initial-mode = <2>;
|
| D | active-semi,act8945a.yaml | 147 regulator-initial-mode = <ACT8945A_REGULATOR_MODE_FIXED>;
165 regulator-initial-mode = <ACT8945A_REGULATOR_MODE_FIXED>;
179 regulator-initial-mode = <ACT8945A_REGULATOR_MODE_FIXED>;
193 regulator-initial-mode = <ACT8945A_REGULATOR_MODE_NORMAL>;
207 regulator-initial-mode = <ACT8945A_REGULATOR_MODE_NORMAL>;
221 regulator-initial-mode = <ACT8945A_REGULATOR_MODE_NORMAL>;
235 regulator-initial-mode = <ACT8945A_REGULATOR_MODE_NORMAL>;
|
| D | wlf,arizona.yaml | 29 Initial data for the LDO1 regulator.
36 Initial data for the MICVDD regulator.
|
| D | ti,tps62870.yaml | 26 regulator-initial-mode:
48 regulator-initial-mode = <1>;
|
| /Documentation/devicetree/bindings/mfd/ |
| D | rohm,bd96801-pmic.yaml | 93 /* 0.5V min INITIAL - 150 mV tune */
99 rohm,initial-voltage-microvolt = <500000>;
110 rohm,initial-voltage-microvolt = <3000000>;
121 rohm,initial-voltage-microvolt = <600000>;
132 rohm,initial-voltage-microvolt = <600000>;
143 rohm,initial-voltage-microvolt = <500000>;
154 rohm,initial-voltage-microvolt = <300000>;
165 rohm,initial-voltage-microvolt = <500000>;
|
| D | rockchip,rk816.yaml | 150 regulator-initial-mode = <1>;
164 regulator-initial-mode = <1>;
176 regulator-initial-mode = <1>;
189 regulator-initial-mode = <1>;
|
| D | ti,twl.yaml | 105 regulator-initial-mode: false
136 regulator-initial-mode: false
188 regulator-initial-mode:
290 regulator-initial-mode = <0xe>;
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-dqevent.rst | 145 called an initial event will be generated for that filehandle with
174 if the HPD is low, then an initial event will be generated for that
183 if the HPD is high, then an initial event will be generated for that
192 if the 5V is low, then an initial event will be generated for that
201 if the 5V is high, then an initial event will be generated for that
213 * .. _`CEC-EVENT-FL-INITIAL-STATE`:
217 - Set for the initial events that are generated when the device is
219 applications to learn the initial state of the CEC adapter at
|
| D | cec-api.rst | 31 - Initial version.
41 Initial revision
|
| /Documentation/process/ |
| D | embargoed-hardware-issues.rst | 95 initial contact, which oversees the process of handling such issues under
99 will form the initial response team for a particular issue. The initial
128 the Contact section above. This initial contact should contain a
136 mailing list which will be used for initial discussion with the reporter,
143 form the initial response team and will be responsible for handling the
144 issue after initial contact. The hardware security team is supporting the
171 The disclosing party provides detailed information to the initial response
181 The initial response team sets up an encrypted mailing-list or repurposes
195 The initial response team will identify further experts from the Linux
275 Neither the hardware security team nor the initial response team assign
[all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | rtc-cmos.txt | 10 - ctrl-reg : Contains the initial value of the control register also
12 - freq-reg : Contains the initial value of the frequency register also
|
| /Documentation/trace/rv/ |
| D | da_monitor_synthesis.rst | 79 This initial implementation presents three different types of monitor instances:
109 When a monitor is enabled, it is placed in the initial state of the automata.
110 However, the monitor does not know if the system is in the *initial state*.
113 monitor that the system is returning to the initial state, so the monitor can
117 the monitor that the system is known to be in the initial state, so the
130 To notify the monitor that the system will be returning to the initial state,
|
| D | da_monitor_instrumentation.rst | 81 Initially, the *model* is placed in the initial state. However, the *system*
82 might or might not be in the initial state. The monitor cannot start
83 processing events until it knows that the system has reached the initial state.
87 and the model are expected to return to the initial state after the
|
| /Documentation/userspace-api/media/rc/ |
| D | remote_controllers.rst | 31 - Initial version.
46 Initial revision
|
| /Documentation/arch/arm/ |
| D | porting.rst | 7 Initial definitions
39 The initial part of the kernel is carefully coded to be position
43 Physical address to place the initial RAM disk. Only relevant if
48 Virtual address of the initial RAM disk. The following constraint
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-controller.rst | 31 - Initial version.
49 Initial revision
|
| /Documentation/networking/ |
| D | mptcp-sysctl.rst | 24 by the initial subflow if the value is 1. This controls a flag that is
40 Initial time period in second to disable MPTCP on active MPTCP sockets
43 MPTCP is re-enabled and will reset to the initial value when the
|
| D | smc-sysctl.rst | 46 Initial size of send buffer used by SMC sockets.
54 Initial size of receive buffer (RMB) used by SMC sockets.
|
| /Documentation/devicetree/bindings/power/avs/ |
| D | qcom,cpr.yaml | 62 - description: Corner 1 initial voltage
63 - description: Corner 2 initial voltage
64 - description: Corner 3 initial voltage
|
| /Documentation/virt/ |
| D | guest-halt-polling.rst | 58 in case of an idle system. This value sets the initial
60 be increased from 10000, to avoid misses during the initial
|
12345678910>>...15