| /linux/drivers/platform/x86/amd/pmf/ |
| H A D | auto-mode.c | 27 data->transition[AUTO_TRANSITION_TO_PERFORMANCE].time_constant); in amd_pmf_dump_auto_mode_defaults()
29 data->transition[AUTO_TRANSITION_FROM_PERFORMANCE_TO_BALANCE].time_constant); in amd_pmf_dump_auto_mode_defaults()
31 data->transition[AUTO_TRANSITION_FROM_QUIET_TO_BALANCE].time_constant); in amd_pmf_dump_auto_mode_defaults()
33 data->transition[AUTO_TRANSITION_TO_QUIET].time_constant); in amd_pmf_dump_auto_mode_defaults()
42 data->transition[AUTO_TRANSITION_TO_PERFORMANCE].power_delta); in amd_pmf_dump_auto_mode_defaults()
44 data->transition[AUTO_TRANSITION_FROM_PERFORMANCE_TO_BALANCE].power_delta); in amd_pmf_dump_auto_mode_defaults()
46 data->transition[AUTO_TRANSITION_FROM_QUIET_TO_BALANCE].power_delta); in amd_pmf_dump_auto_mode_defaults()
48 data->transition[AUTO_TRANSITION_TO_QUIET].power_delta); in amd_pmf_dump_auto_mode_defaults()
160 if ((config_store.transition[i].shifting_up && avg_power >= in amd_pmf_trans_automode()
161 config_store.transition[i].power_threshold) || in amd_pmf_trans_automode()
[all …]
|
| /linux/Documentation/admin-guide/pm/ |
| H A 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 …]
|
| /linux/Documentation/livepatch/ |
| H A 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 …]
|
| H A 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.
|
| H A 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
|
| H A 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
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-livepatch | 28 What: /sys/kernel/livepatch/<patch>/transition
34 transition.
42 course of an existing transition. Writing 1 clears
65 is used, unless a transition is currently in progress.
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A 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
|
| /linux/Documentation/sound/soc/ |
| H A D | dai.rst | 39 transition.
42 MSB is transmitted on transition of LRC.
45 MSB is transmitted sample size BCLKs before LRC transition.
|
| /linux/Documentation/trace/rv/ |
| H A 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
|
| /linux/kernel/livepatch/ |
| H A D | Makefile | 4 livepatch-objs := core.o patch.o shadow.o state.o transition.o
|
| H A D | transition.c | 3 * transition.c - Kernel Live Patching transition functions
15 #include "transition.h"
42 * "straggler" tasks which failed to transition in the first attempt.
78 * The transition to the target patch state is complete. Clean up the data
88 pr_debug("'%s': completing %s transition\n",
107 * func->transition gets cleared, the handler may choose a in klp_complete_transition()
115 func->transition = false; in klp_complete_transition()
151 * This is called in the error path, to cancel a transition before it has in klp_complete_transition()
153 * klp_start_transition() hasn't. If the transition *ha in klp_complete_transition()
[all...] |
| H A D | patch.c | 86 if (unlikely(func->transition)) { in klp_ftrace_handler()
|
| /linux/Documentation/devicetree/bindings/cpufreq/ |
| H A D | cpufreq-spear.txt | 13 - clock-latency: Specify the possible maximum transition latency for clock, in
|
| H A D | nvidia,tegra124-cpufreq.txt | 17 - clock-latency: Specify the possible maximum transition latency for clock,
|
| /linux/Documentation/cpu-freq/ |
| H A D | core.rst | 46 transition notifiers.
63 2.2 CPUFreq transition notifiers
|
| /linux/Documentation/arch/arm/ |
| H A D | cluster-pm-race-avoidance.rst | 136 A trigger event (spontaneous) means that the CPU can transition to the
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
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | keystone-gate.txt | 13 - domain-id : psc domain id needed to check the transition state register
|
| /linux/Documentation/input/devices/ |
| H A 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
|
| /linux/drivers/platform/x86/intel/pmc/ |
| H A D | Kconfig | 17 tasks in the PMC in order to enable transition into the SLPS0 state.
|
| /linux/drivers/net/wireless/broadcom/b43legacy/ |
| H A D | phy.c | 1371 struct b43legacy_lopair transition; in b43legacy_phy_lo_g_state() local
1409 transition.high = tmp_pair.high + in b43legacy_phy_lo_g_state()
1411 transition.low = tmp_pair.low + transitions[j - 1].low; in b43legacy_phy_lo_g_state()
1412 if ((abs(transition.low) < 9) in b43legacy_phy_lo_g_state()
1413 && (abs(transition.high) < 9)) { in b43legacy_phy_lo_g_state()
1414 b43legacy_lo_write(dev, &transition); in b43legacy_phy_lo_g_state()
1423 transition.high; in b43legacy_phy_lo_g_state()
1424 lowest_transition.low = transition.low; in b43legacy_phy_lo_g_state()
|
| /linux/Documentation/hwmon/ |
| H A D | adt7475.rst | 149 This allows smoothing of the fan speed transition. To set the transition time
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | kho.rst | 73 Kexec HandOver (KHO) allows Linux to transition the state of
81 When this file contains "1", the system is in the transition
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | pxa_camera.rst | 79 - each arrow is the condition to transition to another state
80 - an arrow with a comment is a mandatory transition (no condition)
|
| /linux/Documentation/virt/kvm/s390/ |
| H A D | s390-pv.rst | 16 transition into protected mode. On transition, KVM registers the guest
|