Searched full:transition (Results 1 – 25 of 134) sorted by relevance
123456
| /Documentation/admin-guide/pm/ |
| D | suspend-flows.rst | 12 At least one global system-wide transition needs to be carried out for the
15 transition to occur for this purpose, but the other sleep states, commonly
19 For those sleep states, the transition from the working state of the system into
21 of cases, whether this means a transition or a sleep state of the system should
22 be clear from the context) and the transition back from the sleep state into the
45 The following steps are taken in order to transition the system from the working
51 transition is about to occur and when the resume transition has finished.
61 of the transition is in progress (which might have been problematic for
66 transition.
93 deferred till the subsequent system resume transition as described
[all …]
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 85 transition state where tasks are converging to the patched state.
86 Usually this transition state can complete in a few seconds. The same
132 The /sys/kernel/livepatch/<patch>/transition file shows whether a patch
133 is in transition. Only a single patch can be in transition at a given
134 time. A patch can remain in transition indefinitely, if any of the tasks
137 A transition can be reversed and effectively canceled by writing the
139 the transition is in progress. Then all the tasks will attempt to
144 If a patch is in transition, this file shows 0 to indicate the task is
146 transition, it shows -1. Any tasks which are blocking the transition
154 Administrator can also affect a transition through
[all …]
|
| D | cumulative-patches.rst | 15 from all older livepatches and completely replace them in one transition.
30 Once the transition is finished, all older patches are automatically
41 the transition to has finished. It helps to clearly see what code is
74 only when the transition was not forced.
89 for a smooth transition.
|
| D | system-state.rst | 98 - Restore the previous state when the transition is reverted.
119 the new code even before the transition gets finished.
150 - Distinguish transition reverse and livepatch disabling by
153 - In case of transition reverse, restore the previous system
166 It might be called also during the transition reverse. Therefore it
|
| D | callbacks.rst | 79 callback is provided, the transition is assumed to be safe.) If a
94 If a patch transition is reversed, no pre-unpatch handlers will be run
98 If the object did successfully patch, but the patch transition never
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-livepatch | 28 What: /sys/kernel/livepatch/<patch>/transition
34 transition.
42 course of an existing transition. Writing 1 clears
|
| D | sysfs-bus-coresight-devices-etm3x | 177 Description: (RW) Defines the event that causes the sequencer to transition
184 Description: (RW) Defines the event that causes the sequencer to transition
191 Description: (RW) Defines the event that causes the sequencer to transition
198 Description: (RW) Defines the event that causes the sequencer to transition
205 Description: (RW) Defines the event that causes the sequencer to transition
212 Description: (RW) Defines the event that causes the sequencer to transition
|
| /Documentation/sound/soc/ |
| D | dai.rst | 39 transition.
42 MSB is transmitted on transition of LRC.
45 MSB is transmitted sample size BCLKs before LRC transition.
|
| /Documentation/devicetree/bindings/opp/ |
| D | ti,omap-opp-supply.yaml | 14 the primary regulator during an OPP transition.
17 Body Bias regulator, which must transition in a specific sequence
18 w.r.t the vdd-supply and clk when making an OPP transition. By
|
| /Documentation/admin-guide/hw-vuln/ |
| D | cross-thread-rsb.rst | 41 requests to transition out of the C0 state. This can be communicated with the
49 transition between 1T/2T mode, the RAP contents are not modified but the RAP
53 particular, a RET instruction executed immediately after a transition to 1T may
86 attempts to transition out of C0. A VMM can use the KVM_CAP_X86_DISABLE_EXITS
|
| D | mds.rst | 156 transition mitigations are sufficient and SMT is not affected.
163 The protection for host to guest transition depends on the L1TF
170 guest transition.
183 The resulting MDS protection matrix for the host to guest transition:
201 This only covers the host to guest transition, i.e. prevents leakage from
|
| /Documentation/trace/rv/ |
| D | deterministic_automata.rst | 14 - *f* : *X* x *E* -> *X* $ is the transition function. It defines the state
15 transition in the occurrence of an event from *E* in the state *X*. In the
77 unsigned char function[state_max][event_max]; // f: transition function
100 The *transition function* is represented as a matrix of states (lines) and
|
| /Documentation/arch/arm/ |
| D | cluster-pm-race-avoidance.rst | 136 A trigger event (spontaneous) means that the CPU can transition to the
170 Transition of the parent cluster to CLUSTER_UP.
268 further transition possible on the outbound side (i.e., the
288 model. The final transition to CLUSTER_UP/INBOUND_NOT_COMING_UP
298 where the <transitioner> is the side on which the transition
489 __mcpm_cpu_going_down() signals the transition of a CPU to the
492 __mcpm_cpu_down() signals the transition of a CPU to the CPU_DOWN
521 additional topological levels, and modifying the transition
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-spear.txt | 13 - clock-latency: Specify the possible maximum transition latency for clock, in
|
| D | nvidia,tegra124-cpufreq.txt | 17 - clock-latency: Specify the possible maximum transition latency for clock,
|
| D | cpufreq-dt.txt | 17 - clock-latency: Specify the possible maximum transition latency for clock,
|
| /Documentation/devicetree/bindings/clock/ |
| D | keystone-gate.txt | 13 - domain-id : psc domain id needed to check the transition state register
|
| /Documentation/virt/hyperv/ |
| D | coco.rst | 239 the memory isn't in use and isn't referenced while the transition is in
240 progress. The transition has multiple steps, and includes interaction with
255 hypervisor of the transition mark pages as "not present" while a transition
259 encrypted/decrypted transition is complete, the pages are marked as "present"
|
| /Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,od.yaml | 14 Mediatek display overdrive, namely OD, increases the transition values
|
| /Documentation/devicetree/bindings/mfd/ |
| D | twl4030-power.txt | 29 initiate an ACTIVE-to-OFF or SLEEP-to-OFF transition when the
|
| /Documentation/driver-api/soundwire/ |
| D | stream.rst | 237 Below shows the SoundWire stream states and state transition diagram. ::
255 supported at the ALSA/ASoC level. Likewise the transition between
259 NOTE2: The framework implements basic state transition checks, but
260 does not e.g. check if a transition from DISABLED to ENABLED is valid
371 follow the .prepare(), a direct transition from
432 When the INFO_PAUSE flag is supported, a direct transition to
436 stream can transition from ``SDW_STREAM_DISABLED`` to
470 Other implementations may transition to the ``SDW_STREAM_DEPREPARED``
471 state on TRIGGER_STOP, should they require a transition through the
|
| /Documentation/cpu-freq/ |
| D | core.rst | 46 transition notifiers.
63 2.2 CPUFreq transition notifiers
|
| /Documentation/input/devices/ |
| D | rotary-encoder.rst | 61 meaning that there it has seen half the way of a one-step transition.
67 Parking position. If the encoder enters this state, a full transition
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | linux,wdt-gpio.yaml | 25 Either a high-to-low or a low-to-high transition clears the WDT counter.
|
| /Documentation/driver-api/media/ |
| D | tx-rx.rst | 100 proceeds its own part of high speed mode transition.
119 In the context of CSI-2, the ``.pre_streamon()`` callback is used to transition
|
123456