| /Linux-v6.1/Documentation/ABI/testing/ |
| D | debugfs-cros-ec | 40 Some ECs have a feature where they will track transitions to
44 transitions that occurred. The last_resume_result file returns
48 transitions that occurred since the suspend message was
50 system due to a timeout when watching for SLP_S0 transitions.
53 transitions have been attempted, or the EC does not support
62 Some ECs have a feature where they will track transitions of
|
| D | sysfs-class-thermal | 253 transitions. The cat output here is a two dimensional matrix,
255 of transitions from State_i to State_j. If the transition
|
| /Linux-v6.1/Documentation/cpu-freq/ |
| D | cpufreq-stats.rst | 44 about the frequency transitions before the stats driver insertion.
83 This gives the total number of frequency transitions on this CPU. The cat
85 transitions.
95 transitions. The cat output here is a two dimensional matrix, where an entry
96 <i,j> (row i, column j) represents the count of number of transitions from
|
| D | core.rst | 25 frequency transitions), as well as to "notifiers". These are device
|
| /Linux-v6.1/security/safesetid/ |
| D | Kconfig | 3 bool "Gate setid transitions to limit CAP_SET{U/G}ID capabilities"
9 restrict UID/GID transitions from a given UID/GID to only those
|
| /Linux-v6.1/net/llc/ |
| D | llc_s_st.c | 177 .transitions = llc_sap_inactive_state_transitions,
181 .transitions = llc_sap_active_state_transitions,
|
| D | llc_c_st.c | 4900 .transitions = llc_adm_state_transitions,
4904 .transitions = llc_setup_state_transitions,
4908 .transitions = llc_normal_state_transitions,
4912 .transitions = llc_busy_state_transitions,
4916 .transitions = llc_reject_state_transitions,
4920 .transitions = llc_await_state_transitions,
4924 .transitions = llc_await_busy_state_transitions,
4928 .transitions = llc_await_rejct_state_transitions,
4932 .transitions = llc_d_conn_state_transitions,
4936 .transitions = llc_rst_state_transitions,
[all …]
|
| /Linux-v6.1/Documentation/trace/ |
| D | events-power.rst | 5 The power tracing system captures events related to power transitions
11 - Power domains related changes and transitions
64 The power domain events are used for power domains transitions
|
| /Linux-v6.1/net/bridge/ |
| D | br_private_mrp.h | 126 __be16 transitions; member
135 __be16 transitions; member
|
| /Linux-v6.1/include/net/ |
| D | llc_s_st.h | 33 struct llc_sap_state_trans **transitions; member
|
| D | llc_c_st.h | 48 struct llc_conn_state_trans **transitions; member
|
| /Linux-v6.1/Documentation/devicetree/bindings/opp/ |
| D | ti-omap5-opp-supply.txt | 7 an OPP transitions.
12 regulators to the device that will undergo OPP transitions we can make use
|
| /Linux-v6.1/Documentation/core-api/ |
| D | entry.rst | 4 All transitions between execution domains require state updates which are
56 state transitions must run with interrupts disabled.
126 Do not nest KVM entry/exit transitions because doing so is nonsensical.
132 and KVM transitions.
209 NMIs and other NMI-like exceptions handle state transitions without
|
| /Linux-v6.1/Documentation/admin-guide/blockdev/drbd/ |
| D | figures.rst | 17 Sub graphs of DRBD's state transitions
|
| /Linux-v6.1/Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 5 UID/GID transitions from a given UID/GID to only those approved by a
57 to do process spawning and UID/GID transitions). Unfortunately, there are a
90 None of the other in-tree LSMs have the capability to gate setid transitions, or
99 This LSM hooks the setid syscalls to make sure transitions are allowed if an
|
| /Linux-v6.1/Documentation/hwmon/ |
| D | pm6764tr.rst | 29 The PM6764TR supports power state transitions featuring VFDE, and programmable DPM
|
| /Linux-v6.1/tools/testing/selftests/livepatch/ |
| D | README | 43 transitions, sysfs entries, etc.)
|
| /Linux-v6.1/Documentation/arm/ |
| D | cluster-pm-race-avoidance.rst | 292 Details of the allowable transitions follow.
381 transitions to INBOUND_COMING_UP. Alternatively, individual
495 A CPU transitions to CPU_COMING_UP and then to CPU_UP via the
501 handle transitions from CLUSTER_UP to CLUSTER_GOING_DOWN
507 is needed for safe transitions at the cluster level.
509 A cluster transitions from CLUSTER_DOWN back to CLUSTER_UP via
|
| /Linux-v6.1/kernel/time/ |
| D | Kconfig | 139 the expense of some overhead in user <-> kernel transitions:
154 Track transitions between kernel and user on behalf of RCU and
|
| /Linux-v6.1/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,saw2.txt | 5 power-controller that transitions a piece of hardware (like a processor or
|
| /Linux-v6.1/Documentation/power/ |
| D | drivers-testing.rst | 11 resume transitions in a driver, it is necessary to suspend and resume a fully
|
| /Linux-v6.1/tools/kvm/kvm_stat/ |
| D | kvm_stat.txt | 16 state transitions such as guest mode entry and exit.
|
| /Linux-v6.1/Documentation/leds/ |
| D | leds-qcom-lpg.rst | 39 transitions expected by the leds-trigger-pattern format, each entry in the
|
| /Linux-v6.1/Documentation/timers/ |
| D | no_hz.rst | 155 2. The user/kernel transitions are slightly more expensive due
229 * Dyntick-idle slows transitions to and from idle slightly.
253 * Adaptive-ticks slows user/kernel transitions slightly.
255 workloads, which have few such transitions. Careful benchmarking
|
| /Linux-v6.1/Documentation/networking/devlink/ |
| D | devlink-linecard.rst | 72 state transitions::
|
