Home
last modified time | relevance | path

Searched full:sleep (Results 1 – 25 of 2345) sorted by relevance

12345678910>>...94

/linux/arch/arm/boot/dts/st/
H A Dste-nomadik-pinctrl.dtsi54 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 …]
H A Dste-href.dtsi49 pinctrl-names = "default", "sleep";
57 pinctrl-names = "default", "sleep";
63 pinctrl-names = "default", "sleep";
70 pinctrl-names = "default","sleep";
77 pinctrl-names = "default","sleep";
84 pinctrl-names = "default","sleep";
148 pinctrl-names = "default","sleep";
170 pinctrl-names = "default", "sleep";
183 pinctrl-names = "default", "sleep";
200 pinctrl-names = "default", "sleep";
[all …]
/linux/Documentation/devicetree/bindings/pinctrl/
H A Dste,nomadik.txt48 - 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 Dsprd,pinctrl.txt29 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 Dsprd,sc9860-pinctrl.txt26 - 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;
/linux/drivers/net/wwan/iosm/
H A Diosm_ipc_pm.h9 /* 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 …]
H A Diosm_ipc_pm.c79 /* Wait for IPC_PM_ACTIVE_TIMEOUT_MS for Device sleep state in ipc_pm_wait_for_device_active()
102 /* Reset the atomic variable in any case as device sleep in ipc_pm_wait_for_device_active()
115 /* pending sleep ack and all conditions are cleared in ipc_pm_on_link_sleep()
140 * put on hold due to Device sleep state or due to TD update in ipc_pm_on_link_wake()
141 * which could be because of Device Sleep and Host Sleep in ipc_pm_on_link_wake()
169 case IPC_PM_UNIT_HS: /* Host sleep trigger requires Link. */ in ipc_pm_trigger()
224 /* Sending Sleep Exit message to CP. Update the state */ in ipc_pm_prepare_host_active()
230 void ipc_pm_set_s2idle_sleep(struct iosm_pm *ipc_pm, bool sleep) in ipc_pm_set_s2idle_sleep() argument
232 if (sleep) { in ipc_pm_set_s2idle_sleep()
283 "loc-pm=%d sleep: confused req-pm=%d", in ipc_pm_dev_slp_notification()
[all …]
/linux/arch/arm/mach-pxa/
H A Dsleep.S2 * 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 …]
H A Dpxa2xx-regs.h21 #define PSSR __REG(0x40F00004) /* Power Manager Sleep Status Register */
28 #define PGSR0 __REG(0x40F00020) /* Power Manager GPIO Sleep State Register for GP[31-0] */
29 #define PGSR1 __REG(0x40F00024) /* Power Manager GPIO Sleep State Register for GP[63-32] */
30 #define PGSR2 __REG(0x40F00028) /* Power Manager GPIO Sleep State Register for GP[84-64] */
31 #define PGSR3 __REG(0x40F0002C) /* Power Manager GPIO Sleep State Register for GP[118-96] */
34 #define PSLR __REG(0x40F00034) /* Power Manager Sleep Config Register */
90 #define PSSR_SSS (1 << 0) /* Software Sleep Status */
92 #define PSLR_SL_ROD (1 << 20) /* Sleep-Mode/Depp-Sleep Mode nRESET_OUT Disable */
97 #define PCFR_L1_EN (1 << 11) /* Sleep Mode L1 converter Enable */
99 #define PCFR_DC_EN (1 << 7) /* Sleep/deep-sleep DC-DC Converter Enable */
[all …]
/linux/tools/power/cpupower/man/
H A Dcpupower-idle-set.111 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 Dcpupower-monitor.122 \fBcpupower-monitor \fP implements independent processor sleep state and
72 This is to wake up the processors from deeper sleep states and let the
102 any sleep state) times. These counters do not have the inaccuracy restrictions
109 Intel Core and Package sleep state counters.
112 Deepest package sleep states may in reality show up as machine/platform wide
113 sleep states and can only be entered if all cores are idle. Look up Intel
115 The monitors are named after the CPU family where the sleep state capabilities
117 For example an IvyBridge processor has sleep state capabilities which got
119 Thus on an IvyBridge processor one will get Nehalem and SandyBridge sleep
121 HaswellExtended extra package sleep state capabilities are available only in a
[all …]
H A Dcpupower-idle-info.124 CPU sleep state statistics and descriptions are retrieved from sysfs files,
28 good overview about the usage and availability of processor sleep states on
31 Be aware that the sleep states as exported by the hardware or BIOS and used by
37 which monitor the duration of sleep states the processor resided in. The
38 cpupower monitor tool (cpupower\-monitor(1)) can be used to show real sleep
57 The acpi_idle cpuidle driver retrieves available sleep states (C\-states) from
69 The intel_idle driver knows the sleep state capabilities of the processor and
70 ignores ACPI BIOS exported processor sleep states tables.
/linux/Documentation/devicetree/bindings/powerpc/fsl/
H A Dpmc.yaml16 Sleep of peripheral devices is configured by the `sleep` property, for
17 example `sleep = <&pmc 0x00000030>`. Any cells after the &pmc phandle are
18 called a sleep specifier.
20 For "fsl,mpc8349-pmc", sleep specifiers consist of one cell. For each bit that
22 on suspend, and restored on resume. This sleep controller supports disabling
25 For "fsl,mpc8536-pmc", sleep specifiers consist of three cells, the third of
28 sleep controller only supports disabling devices during system sleep, or
31 For "fsl,mpc8548-pmc" or "fsl,mpc8641d-pmc", Sleep specifiers consist of one
35 disabling. This sleep controller does not support configuring devices to
36 disable during system sleep (unless supported by another compatible match),
[all …]
/linux/tools/testing/selftests/net/
H A Dfcnal-test.sh544 sleep 1
578 sleep 1
2100 sleep 3
2102 sleep 1
2114 sleep 3
2116 sleep 1
2127 sleep 3
2129 sleep 1
2141 sleep 3
2143 sleep
[all...]
H A Dlwt_dst_cache_ref_loop.sh120 sleep 1
128 sleep 1
149 sleep 1
153 sleep 1
157 sleep 1
170 sleep 1
174 sleep 1
188 sleep 1
192 sleep 1
196 sleep 1
[all …]
/linux/kernel/time/
H A Dsleep_timeout.c31 * schedule_timeout - sleep until timeout
34 * Make the current task sleep until @timeout jiffies have elapsed.
38 * %TASK_RUNNING - the scheduler is called, but the task does not sleep
118 * schedule_timeout_interruptible - sleep until timeout (interruptible)
133 * schedule_timeout_killable - sleep until timeout (killable)
148 * schedule_timeout_uninterruptible - sleep until timeout (uninterruptible)
163 * schedule_timeout_idle - sleep until timeout (idle)
180 * schedule_hrtimeout_range_clock - sleep until timeout
228 * schedule_hrtimeout_range - sleep until timeout
233 * Make the current task sleep until the given expiry time has
[all …]
/linux/tools/power/cpupower/bench/
H A DREADME-BENCH34 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 …]
/linux/Documentation/devicetree/bindings/powerpc/
H A Dsleep.yaml4 $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 …]
/linux/tools/testing/selftests/net/mptcp/
H A Duserspace_pm.sh181 sleep 0.5
214 sleep 0.5
222 sleep 1
341 sleep 0.5
350 sleep 0.5
360 sleep 0.5
371 sleep 0.5
380 sleep 0.5
390 sleep 0.5
451 sleep 0.5
[all …]
/linux/Documentation/admin-guide/
H A Dbtmrvl.rst13 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 …]
/linux/include/linux/
H A Dwait.h334 * wait_event - sleep until a condition gets true
338 * The process is put to sleep (TASK_UNINTERRUPTIBLE) until the
373 * wait_event_freezable - sleep (or freeze) until a condition gets true
377 * The process is put to sleep (TASK_INTERRUPTIBLE -- so as not to contribute
399 * wait_event_timeout - sleep until a condition gets true or a timeout elapses
404 * The process is put to sleep (TASK_UNINTERRUPTIBLE) until the
462 * wait_event_cmd - sleep until a condition gets true
465 * @cmd1: the command will be executed before sleep
466 * @cmd2: the command will be executed after sleep
468 * The process is put to sleep (TASK_UNINTERRUPTIBLE) until the
[all …]
/linux/Documentation/admin-guide/pm/
H A Dstrategies.rst17 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
/linux/tools/perf/tests/shell/
H A Dftrace.sh34 sleep_functions=$(grep 'sys_.*sleep$' "${output}")
35 echo "syscalls for sleep:"
42 perf ftrace trace --graph-opts depth=5 sleep 0.1 > "${output}"
43 # it should have some function name contains 'sleep'
45 grep -F 'sleep()' "${output}"
55 echo "perf ftrace trace test [Failure: sleep syscall not found]"
62 perf ftrace latency -T "${target_function}" sleep 0.1 > "${output}"
70 perf ftrace profile --graph-opts depth=5 sleep 0.1 > "${output}"
/linux/tools/testing/selftests/ftrace/test.d/trigger/
H A Dtrigger-hist-poll.tc31 echo 'hist:key=comm if comm =="sleep"' > ${EVENT}/trigger
34 # This sleep command will exit after 2 seconds.
35 sleep 2 &
47 if ! grep -qw "sleep" trace; then
56 # This sleep command will exit after 2 seconds.
57 sleep 2 &
69 if ! grep -qw "sleep" trace; then
/linux/arch/powerpc/boot/dts/fsl/
H A Dmpc8568si-post.dtsi40 sleep = <&pmc 0x08000000>;
52 sleep = <&pmc 0x80000000>;
64 sleep = <&pmc 0x20000000>;
90 sleep = <&pmc 0x00080000>;
125 i2c-sleep-nexus {
129 sleep = <&pmc 0x00000004>;
137 duart-sleep-nexus {
141 sleep = <&pmc 0x00000002>;
158 sleep = <&pmc 0x00000400>;
163 sleep = <&pmc 0x00000080>;
[all …]

12345678910>>...94