| /linux-4.1.27/Documentation/cpu-freq/ |
| D | cpufreq-stats.txt | 39 driver will not have any information about the frequency transitions before
70 This gives the total number of frequency transitions on this CPU. The cat
72 transitions.
81 transitions. The cat output here is a two dimensional matrix, where an entry
82 <i,j> (row i, column j) represents the count of number of transitions from
|
| D | amd-powernow.txt | 18 Frequency transitions will be unavailable if the BIOS does
|
| D | core.txt | 31 frequency transitions), as well as to "notifiers". These are device
|
| /linux-4.1.27/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 …]
|
| D | llc_conn.c | 418 for (next_trans = curr_state->transitions + in llc_qualify_conn_ev()
648 for (next_trans = state->transitions + offset; in llc_find_next_offset()
|
| D | llc_sap.c | 127 for (next_trans = curr_state->transitions; next_trans[i]->ev; i++) in llc_find_sap_trans()
|
| /linux-4.1.27/include/net/ |
| D | llc_s_st.h | 27 struct llc_sap_state_trans **transitions; member
|
| D | llc_c_st.h | 44 struct llc_conn_state_trans **transitions; member
|
| /linux-4.1.27/Documentation/trace/ |
| D | events-power.txt | 4 The power tracing system captures events related to power transitions
10 o Power domains related changes and transitions
59 The power domain events are used for power domains transitions
|
| /linux-4.1.27/Documentation/blockdev/drbd/ |
| D | README.txt | 16 The sub graphs of DRBD's state transitions
|
| /linux-4.1.27/Documentation/power/ |
| D | states.txt | 53 and all low-level system functions are suspended during transitions into this
66 when entering Power-On Suspend are also carried out during transitions to STR.
69 firmware) as the last step during STR transitions and that usually results in
|
| D | drivers-testing.txt | 7 resume transitions in a driver, it is necessary to suspend and resume a fully
|
| D | devices.txt | 51 transitions (suspend or hibernation).
121 system-wide power transitions.
220 power transitions. In particular, the device can (and in the majority of cases
609 for the given device during all power transitions, instead of the respective
|
| D | pm_qos_interface.txt | 211 state changes (e.g. during transitions from D3cold to D0), which generally may
|
| D | pci.txt | 109 possible power state transitions the device can undergo are the following:
347 during system-wide transitions to a sleep state and back to the working state.
419 There are a few different types of system-wide power transitions, described in
|
| D | runtime_pm.txt | 15 them to be synchronized with system-wide power transitions (suspend to RAM,
664 as appropriate. This only applies to system suspend transitions that are not
|
| /linux-4.1.27/fs/fscache/ |
| D | object.c | 70 .transitions = { __VA_ARGS__, { 0, NULL } } \
205 for (t = state->transitions; t->events; t++) { in fscache_object_sm_dispatcher()
251 for (t = state->transitions; t->events; t++) in fscache_object_sm_dispatcher()
325 for (t = object->state->transitions; t->events; t++) in fscache_object_init()
|
| /linux-4.1.27/Documentation/arm/ |
| D | cluster-pm-race-avoidance.txt | 276 Details of the allowable transitions follow.
355 transitions to INBOUND_COMING_UP. Alternatively, individual
460 A CPU transitions to CPU_COMING_UP and then to CPU_UP via the
466 handle transitions from CLUSTER_UP to CLUSTER_GOING_DOWN
472 is needed for safe transitions at the cluster level.
474 A cluster transitions from CLUSTER_DOWN back to CLUSTER_UP via
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,saw2.txt | 5 power-controller that transitions a piece of hardware (like a processor or
|
| /linux-4.1.27/drivers/cpufreq/ |
| D | Kconfig | 153 transitions).
177 transitions in the CPU) you will probably want to use this governor.
|
| /linux-4.1.27/Documentation/timers/ |
| D | NO_HZ.txt | 157 2. The user/kernel transitions are slightly more expensive due
257 o Dyntick-idle slows transitions to and from idle slightly.
281 o Adaptive-ticks slows user/kernel transitions slightly.
283 workloads, which have few such transitions. Careful benchmarking
|
| /linux-4.1.27/tools/perf/Documentation/ |
| D | perf-timechart.txt | 49 Don't output processor state transitions
|
| /linux-4.1.27/include/linux/ |
| D | fscache-cache.h | 342 const struct fscache_transition transitions[]; member
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-class-devfreq | 53 the number of transitions between states.
|
| D | sysfs-devices-power | 62 transitions (eg. suspend to RAM, hibernation).
180 opportunistic transitions to sleep states from occurring.
|
| D | sysfs-firmware-acpi | 10 transitions.
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | freezer-subsystem.txt | 66 FREEZING cgroup transitions into FROZEN state when all tasks
|
| /linux-4.1.27/Documentation/scsi/ |
| D | scsi_fc_transport.txt | 252 The following state table indicates the different state transitions:
279 The following 4 error states all have the same transitions:
359 - Kick of further vport state transitions based on the disable flag and
|
| D | ChangeLog.lpfc | 856 * Fixed link down->up transitions when linkdown tmo expires. Fix
|
| /linux-4.1.27/kernel/time/ |
| D | Kconfig | 114 transitions: syscalls, exceptions and interrupts. Even when it's
|
| /linux-4.1.27/Documentation/locking/ |
| D | mutex-design.txt | 26 transitions that can occur during the lifetime of a lock:
|
| /linux-4.1.27/Documentation/ |
| D | SubmittingDrivers | 93 system-wide suspend and resume transitions. You should verify
|
| D | md.txt | 260 cannot be explicitly set, and some transitions are not allowed.
|
| /linux-4.1.27/drivers/net/wireless/b43legacy/ |
| D | phy.c | 1381 static const struct b43legacy_lopair transitions[8] = { in b43legacy_phy_lo_g_state() local
1435 transitions[j - 1].high; in b43legacy_phy_lo_g_state()
1436 transition.low = tmp_pair.low + transitions[j - 1].low; in b43legacy_phy_lo_g_state()
|
| /linux-4.1.27/Documentation/arm/OMAP/ |
| D | DSS | 90 then, the state transitions to _CONFIGURED, and then, when it is ready to
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | cachefiles.txt | 348 SELinux transitions the daemon's security ID to the module's security ID
|
| /linux-4.1.27/init/ |
| D | Kconfig | 358 kernel entry and exit and on transitions within the kernel
388 transitions between softirq and hardirq state, so there can be a
|
| /linux-4.1.27/scripts/kconfig/ |
| D | zconf.lex.c_shipped | 1364 * (since all states make transitions on EOB to the
|
| /linux-4.1.27/arch/blackfin/ |
| D | Kconfig | 1440 manuals. There is a theoretical risk that during VDDINT transitions
|
| /linux-4.1.27/scripts/genksyms/ |
| D | lex.lex.c_shipped | 937 * (since all states make transitions on EOB to the
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-lexer.lex.c_shipped | 1240 * (since all states make transitions on EOB to the
|
| /linux-4.1.27/drivers/watchdog/ |
| D | Kconfig | 1336 position represented by this number transitions from zero to one.
|
| /linux-4.1.27/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 1279 ThinkPads while the EC transitions the PWM to offline mode,
|
| /linux-4.1.27/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 803 * In the A, the LQO manager transitions to LQOSTOP0 even if
|