| /Linux-v5.10/arch/arm/boot/dts/ |
| 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 …]
|
| D | ste-href.dtsi | 17 pinctrl-names = "default", "sleep";
25 pinctrl-names = "default", "sleep";
31 pinctrl-names = "default", "sleep";
38 pinctrl-names = "default","sleep";
45 pinctrl-names = "default","sleep";
52 pinctrl-names = "default","sleep";
110 pinctrl-names = "default","sleep";
147 pinctrl-names = "default", "sleep";
160 pinctrl-names = "default", "sleep";
175 pinctrl-names = "default", "sleep";
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/pinctrl/ |
| 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 …]
|
| 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 …]
|
| 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;
|
| /Linux-v5.10/Documentation/devicetree/bindings/mfd/ |
| 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 …]
|
| /Linux-v5.10/arch/arm/mach-pxa/ |
| D | sleep.S | 2 * Low-level PXA250/210 sleep/wakeUp support
27 * pxa3xx_finish_suspend() - forces CPU into sleep state (S2D3C4)
31 mcr p14, 0, r0, c7, c0, 0 @ enter sleep
33 20: b 20b @ waiting for sleep
40 * Forces CPU into sleep state.
42 * r0 = value for PWRMODE M field for desired sleep state
45 @ Put the processor to sleep
48 @ prepare value for sleep mode
49 mov r1, r0 @ sleep mode
67 @ (see Errata 50, ...processor does not exit from sleep...)
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/powerpc/fsl/ |
| 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 …]
|
| /Linux-v5.10/tools/power/cpupower/man/ |
| 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 …]
|
| 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 …]
|
| D | cpupower-idle-info.1 | 24 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-v5.10/Documentation/devicetree/bindings/powerpc/ |
| 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 …]
|
| /Linux-v5.10/tools/testing/selftests/net/ |
| D | fcnal-test.sh | 179 sleep 1
493 sleep 1
523 sleep 1
805 sleep 1
813 sleep 1
821 sleep 1
829 sleep 1
840 sleep 1
848 sleep 1
856 sleep 1
[all …]
|
| /Linux-v5.10/tools/power/cpupower/bench/ |
| 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 …]
|
| D | main.c | 20 {"sleep", 1, 0, 's'},
30 {"sleep-step", 1, 0, 'y'},
44 printf(" -s, --sleep=<long int>\t\tinitial sleep time in us\n"); in usage()
46 printf(" -y, --sleep-step=<long int>\ttime to be added to sleep time, in us\n"); in usage()
50 printf(" -n, --cycles=<int>\t\t\tload/sleep cycles\n"); in usage()
51 printf(" -r, --rounds<int>\t\t\tload/sleep rounds\n"); in usage()
93 sscanf(optarg, "%li", &config->sleep); in main()
94 dprintf("user sleep time -> %s\n", optarg); in main()
160 "sleep=%li\n\t" in main()
168 config->sleep, in main()
|
| /Linux-v5.10/Documentation/locking/ |
| 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).
96 the caller must not sleep, and is advised to release the hwspinlock as
102 The function will never sleep.
112 interrupts are disabled, so the caller must not sleep, and is advised to
117 The function will never sleep.
129 given flags placeholder. The caller must not sleep, and is advised to
135 The function will never sleep.
[all …]
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| 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 …]
|
| /Linux-v5.10/Documentation/admin-guide/ |
| 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 …]
|
| /Linux-v5.10/include/linux/ |
| D | wait.h | 293 * wait_event - sleep until a condition gets true
297 * The process is put to sleep (TASK_UNINTERRUPTIBLE) until the
332 * wait_event_freezable - sleep (or freeze) until a condition gets true
336 * The process is put to sleep (TASK_INTERRUPTIBLE -- so as not to contribute
358 * wait_event_timeout - sleep until a condition gets true or a timeout elapses
363 * The process is put to sleep (TASK_UNINTERRUPTIBLE) until the
421 * wait_event_cmd - sleep until a condition gets true
424 * @cmd1: the command will be executed before sleep
425 * @cmd2: the command will be executed after sleep
427 * The process is put to sleep (TASK_UNINTERRUPTIBLE) until the
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/pm/ |
| 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
|
| D | suspend-flows.rst | 14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
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
20 the target sleep state is referred to as *system suspend* too (in the majority
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
26 different sleep states of the system are quite similar, but there are some
29 :ref:`standby <standby>` sleep states.
31 The :ref:`suspend-to-RAM <s2ram>` and :ref:`standby <standby>` sleep states
35 available. Apart from that, the suspend and resume code flows for these sleep
[all …]
|
| /Linux-v5.10/tools/perf/examples/bpf/ |
| D | 5sec.c | 6 just some (-e *sleep).
11 . Run it system wide, so that any sleep of >= 5 seconds and < than 6
16 . While this is running, run something like "sleep 5s".
32 rpl_nanosleep (/usr/bin/sleep)
33 xnanosleep (/usr/bin/sleep)
34 main (/usr/bin/sleep)
36 _start (/usr/bin/sleep)
|
| /Linux-v5.10/arch/powerpc/boot/dts/fsl/ |
| D | mpc8568si-post.dtsi | 40 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 …]
|
| /Linux-v5.10/tools/testing/selftests/net/mptcp/ |
| D | diag.sh | 13 # mptcp_connect in join mode will sleep a bit before completing,
15 sleep 1.1
83 sleep 0.1
88 sleep 0.1
98 sleep 0.1
101 sleep 0.1
110 sleep 0.1
116 sleep 1.5
|
| /Linux-v5.10/arch/arm/mach-s3c/ |
| D | sleep-s3c2410.S | 8 * Based on PXA/SA1100 sleep code by:
25 * put the cpu into sleep mode
29 @@ prepare cpu to sleep
38 orr r7, r7, #S3C2410_REFRESH_SELF @ SDRAM sleep command
50 streq r7, [r4] @ SDRAM sleep command
52 streq r9, [r6] @ CPU sleep
|
