| /openbmc/linux/arch/arm/boot/dts/st/ |
| H A D | ste-nomadik-pinctrl.dtsi | 54 ste,sleep = <SLPM_ENABLED>;
55 ste,sleep-wakeup = <SLPM_WAKEUP_DISABLE>;
56 ste,sleep-pull-disable = <SLPM_PDIS_DISABLED>;
60 ste,sleep = <SLPM_ENABLED>;
61 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
62 ste,sleep-pull-disable = <SLPM_PDIS_DISABLED>;
66 ste,sleep = <SLPM_ENABLED>;
67 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
68 ste,sleep-pull-disable = <SLPM_PDIS_ENABLED>;
72 ste,sleep = <SLPM_ENABLED>;
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | ste,nomadik.txt | 48 - ste,sleep: <0/1>
49 0: sleep mode disable,
50 1: sleep mode enable.
52 - ste,sleep-input: <0/1/2/3>
53 0: sleep input with no pull,
54 1: sleep input with pull up,
55 2: sleep input with pull down.
56 3: sleep input and keep last input configuration (no pull, pull up or pull down).
58 - ste,sleep-output: <0/1/2>
59 0: sleep output low,
[all …]
|
| H A D | sprd,pinctrl.txt | 29 to configure the pin sleep mode, function select and sleep related
32 Now we have 4 systems for sleep mode on SC9860 SoC: AP system,
33 PUBCP system, TGLDSP system and AGDSP system. And the pin sleep
42 In some situation we need set the pin sleep mode and pin sleep related
43 configuration, to set the pin sleep related configuration automatically
44 by hardware when the system specified by sleep mode goes into deep
45 sleep mode. For example, if we set the pin sleep mode as PUBCP_SLEEP
46 and set the pin sleep related configuration as "input-enable", which
47 means when PUBCP system goes into deep sleep mode, this pin will be set
50 Moreover we can not use the "sleep" state, since some systems (like:
[all …]
|
| H A D | sprd,sc9860-pinctrl.txt | 26 - sleep-hardware-state: Indicate these configs in this state are sleep related.
28 - sprd,sleep-mode: Choose the pin sleep mode, and supported values are:
31 Pin sleep mode definition:
52 sprd,sleep-mode = <AP_SLEEP | PUBCP_SLEEP>;
55 sleep-hardware-state;
66 sleep-hardware-state;
|
| /openbmc/linux/drivers/net/wwan/iosm/ |
| H A D | iosm_ipc_pm.h | 9 /* Trigger the doorbell interrupt on cp to change the PM sleep/active status */
18 * union ipc_pm_cond - Conditions for D3 and the sleep message to CP.
21 * @hs: Host Sleep
35 * enum ipc_mem_host_pm_state - Possible states of the HOST SLEEP finite state
41 * before going into sleep
43 * before going to sleep
47 * sleep
59 * enum ipc_mem_dev_pm_state - Possible states of the DEVICE SLEEP finite state
67 * sleep.
89 * @host_sleep_pend: Variable to indicate Host Sleep Pending
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | tps65910.txt | 60 - ti,en-gpio-sleep: enable sleep control for gpios
64 - ti,sleep-enable: Enable SLEEP state.
65 - ti,sleep-keep-therm: Keep thermal monitoring on in sleep state.
66 - ti,sleep-keep-ck32k: Keep the 32KHz clock output on in sleep state.
67 - ti,sleep-keep-hsclk: Keep high speed internal clock on in sleep state.
70 - ti,regulator-ext-sleep-control: enable external sleep
93 ti,en-gpio-sleep = <0 0 1 0 0 0 0 0 0>;
115 ti,regulator-ext-sleep-control = <0>;
124 ti,regulator-ext-sleep-control = <4>;
133 ti,regulator-ext-sleep-control = <0>;
[all …]
|
| /openbmc/linux/arch/arm/mach-pxa/ |
| H A D | sleep.S | 2 * Low-level PXA250/210 sleep/wakeUp support
28 * pxa3xx_finish_suspend() - forces CPU into sleep state (S2D3C4)
32 mcr p14, 0, r0, c7, c0, 0 @ enter sleep
34 20: b 20b @ waiting for sleep
41 * Forces CPU into sleep state.
43 * r0 = value for PWRMODE M field for desired sleep state
46 @ Put the processor to sleep
49 @ prepare value for sleep mode
50 mov r1, r0 @ sleep mode
68 @ (see Errata 50, ...processor does not exit from sleep...)
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | pmc.txt | 8 whose PMC is compatible, and implies deep-sleep capability.
12 whose PMC is compatible, and implies deep-sleep capability.
19 bit assignments are indicated via the sleep specifier in each device's
20 sleep property.
34 a wakeup source from deep sleep.
36 Sleep specifiers:
38 fsl,mpc8349-pmc: Sleep specifiers consist of one cell. For each bit
40 and cleared on suspend, and restored on resume. This sleep controller
43 fsl,mpc8536-pmc: Sleep specifiers consist of three cells, the third of
46 This sleep controller only supports disabling devices during system
[all …]
|
| /openbmc/linux/tools/power/cpupower/man/ |
| H A D | cpupower-idle-set.1 | 11 sleep state, specific options offered by the kernel. One example is disabling
12 sleep states. This can be handy for power vs performance tuning.
17 Disable a specific processor sleep state.
20 Enable a specific processor sleep state.
32 Cpuidle Governors Policy on Disabling Sleep States
36 how to choose sleep states, subsequent sleep states on this core, might get
50 Disabling the Lightest Sleep State may not have any Affect
53 If criteria are not met to enter deeper sleep states and the lightest sleep
54 state is chosen when idle, the kernel may still enter this sleep state,
56 the usage count of the disabled sleep state when using the cpupower idle-info
[all …]
|
| H A D | cpupower-monitor.1 | 22 \fBcpupower-monitor \fP implements independent processor sleep state and
72 This is to wake up the processors from deeper sleep states and let the
107 any sleep state) times. These counters do not have the inaccuracy restrictions
114 Intel Core and Package sleep state counters.
117 Deepest package sleep states may in reality show up as machine/platform wide
118 sleep states and can only be entered if all cores are idle. Look up Intel
120 The monitors are named after the CPU family where the sleep state capabilities
122 For example an IvyBridge processor has sleep state capabilities which got
124 Thus on an IvyBridge processor one will get Nehalem and SandyBridge sleep
126 HaswellExtended extra package sleep state capabilities are available only in a
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/ |
| H A D | sleep.yaml | 4 $id: http://devicetree.org/schemas/powerpc/sleep.yaml#
7 title: PowerPC sleep property
17 may contain a "sleep" property which describes these connections.
19 The sleep property consists of one or more sleep resources, each of
20 which consists of a phandle to a sleep controller, followed by a
21 controller-specific sleep specifier of zero or more cells.
24 by the sleep controller. Some examples of the types of low power modes
35 such nodes should be placed on a virtual bus, where the bus has the sleep
37 reasonably grouped in this manner, then create a virtual sleep controller
39 sleep-map should wait until its necessity is demonstrated).
[all …]
|
| /openbmc/linux/tools/power/cpupower/bench/ |
| H A D | README-BENCH | 34 You can specify load (100% CPU load) and sleep (0% CPU load) times in us which
37 sleep=25000
41 This part of the configuration file will create 25ms load/sleep turns,
48 Will increase load and sleep time by 25ms 5 times.
50 25ms load/sleep time repeated 20 times (cycles).
51 50ms load/sleep time repeated 20 times (cycles).
53 100ms load/sleep time repeated 20 times (cycles).
69 100% CPU load (load) | 0 % CPU load (sleep) | round
79 In round 2, if the ondemand sampling times exactly match the load/sleep
83 But if ondemand always kicks in in the middle of the load sleep cycles, it
[all …]
|
| /openbmc/linux/tools/testing/selftests/net/ |
| H A D | fcnal-test.sh | 197 sleep 1
536 sleep 1
566 sleep 1
868 sleep 1
876 sleep 1
884 sleep 1
892 sleep 1
903 sleep 1
911 sleep 1
919 sleep 1
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/state/phosphor-state-manager/ |
| H A D | power-cmd | 34 sleep 6
36 sleep 1
44 sleep 1
46 sleep 1
49 sleep 10
57 sleep 1
59 sleep 1
63 sleep 1
79 sleep 1
81 sleep 1
|
| /openbmc/linux/Documentation/locking/ |
| H A D | hwspinlock.rst | 50 Should be called from a process context (might sleep).
61 Should be called from a process context (might sleep).
76 Should be called from a process context (might sleep).
86 Should be called from a process context (might sleep).
97 Should be called from a process context (might sleep).
107 the caller must not sleep, and is advised to release the hwspinlock as
113 The function will never sleep.
123 interrupts are disabled, so the caller must not sleep, and is advised to
128 The function will never sleep.
140 given flags placeholder. The caller must not sleep, and is advised to
[all …]
|
| /openbmc/linux/tools/testing/selftests/net/mptcp/ |
| H A D | userspace_pm.sh | 209 sleep 0.5
215 sleep 0.5
223 sleep 1
366 sleep 0.5
375 sleep 0.5
385 sleep 0.5
396 sleep 0.5
405 sleep 0.5
415 sleep 0.5
476 sleep 0.5
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | btmrvl.rst | 13 These commands are used to configure the host sleep parameters::
22 wakeup event, or 0xff for special host sleep setting.
35 These commands are used to enable/disable auto sleep mode
39 1 -- Enable auto sleep mode
40 0 -- Disable auto sleep mode
44 # Enable auto sleep mode
48 # Disable auto sleep mode
54 These commands are used to enable host sleep or wake up firmware
58 1 -- Enable host sleep
63 # Enable host sleep
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-power | 15 from sleep states, such as the memory sleep state (suspend to
20 used to activate the system from a sleep state. Such devices
33 be enabled to wake up the system from sleep states.
87 the system from sleep states, this attribute is not present.
88 If the device is not enabled to wake up the system from sleep
99 system from sleep states, this attribute is not present. If
100 the device is not enabled to wake up the system from sleep
109 the device might have aborted system transition into a sleep
111 is not capable to wake up the system from sleep states, this
113 up the system from sleep states, this attribute is empty.
[all …]
|
| /openbmc/qemu/tests/rocker/ |
| H A D | bridge-stp | 4 sleep 10
5 while ! simp ssh tut sw1 --cmd "ping -c 1 localhost >/dev/null"; do sleep 1; done
6 while ! simp ssh tut h1 --cmd "ping -c 1 localhost >/dev/null"; do sleep 1; done
7 while ! simp ssh tut h2 --cmd "ping -c 1 localhost >/dev/null"; do sleep 1; done
43 sleep 10
45 sleep 10
47 sleep 10
49 sleep 10
51 sleep 10
|
| H A D | bridge-vlan-stp | 4 sleep 10
5 while ! simp ssh tut sw1 --cmd "ping -c 1 localhost >/dev/null"; do sleep 1; done
6 while ! simp ssh tut h1 --cmd "ping -c 1 localhost >/dev/null"; do sleep 1; done
7 while ! simp ssh tut h2 --cmd "ping -c 1 localhost >/dev/null"; do sleep 1; done
55 sleep 10
57 sleep 10
59 sleep 10
61 sleep 10
63 sleep 10
|
| /openbmc/u-boot/arch/x86/include/asm/ |
| H A D | acpi_s3.h | 49 * acpi_ss_string() - get ACPI-defined sleep state string
51 * @pm1_cnt: ACPI-defined sleep state
52 * @return: a pointer to the sleep state string.
62 * acpi_sleep_from_pm1() - get ACPI-defined sleep state from PM1_CNT register
65 * @return: ACPI-defined sleep state if given valid PM1_CNT register value,
87 * chipset_prev_sleep_state() - Get chipset previous sleep state
89 * This returns chipset previous sleep state from ACPI registers.
97 * chipset_clear_sleep_state() - Clear chipset sleep state
99 * This clears chipset sleep state in ACPI registers.
|
| /openbmc/linux/include/linux/ |
| H A D | wait.h | 333 * wait_event - sleep until a condition gets true
337 * The process is put to sleep (TASK_UNINTERRUPTIBLE) until the
372 * wait_event_freezable - sleep (or freeze) until a condition gets true
376 * The process is put to sleep (TASK_INTERRUPTIBLE -- so as not to contribute
398 * wait_event_timeout - sleep until a condition gets true or a timeout elapses
403 * The process is put to sleep (TASK_UNINTERRUPTIBLE) until the
461 * wait_event_cmd - sleep until a condition gets true
464 * @cmd1: the command will be executed before sleep
465 * @cmd2: the command will be executed after sleep
467 * The process is put to sleep (TASK_UNINTERRUPTIBL
[all...] |
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | strategies.rst | 17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
21 user space code can run. Because sleep states are global and the whole system
40 as a whole is regarded as "runtime idle" which may be very close to a sleep
43 for the same system in a sleep state. However, transitions from sleep states
45 typically the system can spend much more time in a sleep state than it can be
47 sleep states than when they are runtime idle most of the time.
52 go into a sleep state at that point. On the other hand, if the user simply goes
|
| /openbmc/openbmc/meta-facebook/meta-bletchley/recipes-bletchley/plat-tools/files/ |
| H A D | bletchley-usbmux-util | 54 sleep 2
61 sleep 2
68 sleep 2
75 sleep 2
82 sleep 2
89 sleep 2
115 sleep 1
|
| /openbmc/openbmc/meta-facebook/meta-tiogapass/recipes-phosphor/flash/phosphor-software-manager/ |
| H A D | bios-update | 67 sleep 15
80 sleep 5
89 sleep 1
116 sleep 1
119 sleep 10
124 sleep 5
130 sleep 10
135 sleep 5
140 sleep 5
|