Searched full:sleep (Results 1 – 25 of 348) sorted by relevance
12345678910>>...14
| /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;
|
| /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 …]
|
| /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 …]
|
| /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 …]
|
| D | rockchip,rk817.yaml | 141 rockchip,sleep-enter-current-microamp:
143 Value in microamps of the sleep enter current for the charger.
146 rockchip,sleep-filter-current-microamp:
148 Value in microamps of the sleep filter current for the charger.
149 Value is used by the driver to derive the sleep sample current.
154 - rockchip,sleep-enter-current-microamp
155 - rockchip,sleep-filter-current-microamp
385 rockchip,sleep-enter-current-microamp = <300000>;
386 rockchip,sleep-filter-current-microamp = <100000>;
|
| /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 …]
|
| /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).
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 …]
|
| /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 …]
|
| D | sleep-states.rst | 5 System Sleep States
13 Sleep states are global low-power states of the entire system in which user
18 Sleep States That Can Be Supported
22 the Linux kernel can support up to four system sleep states, including
23 hibernation and up to three variants of system suspend. The sleep states that
157 interface for system sleep regardless of the underlying system architecture or
163 This file contains a list of strings representing sleep states supported
165 to start a transition of the system into the sleep state represented by
170 :ref:`standby <standby>` sleep states, respectively. The "mem" string
174 If the kernel does not support any system sleep states, this file is
[all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom-stats.yaml | 14 sleep modes involving powering down of the rails and oscillator clock.
16 Statistics includes SoC sleep mode type, number of times low power mode were
17 entered, time of last entry, time of last exit and accumulated sleep duration.
25 # For older RPM firmware versions with fixed offset for the sleep stats
55 # Example of rpmh sleep stats
61 # Example of rpm sleep stats
|
| /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 …]
|
| D | debugfs-cros-ec | 63 a hardware-controlled sleep line, such as Intel's SLP_S0 line,
65 sleep states. The suspend_timeout_ms file controls the amount of
66 time in milliseconds the EC will wait before declaring a sleep
70 65535 (EC_HOST_SLEEP_TIMEOUT_INFINITE) to disable the EC sleep
73 sleep transition before declaring a timeout. This includes both
74 the duration after a sleep command was received but before the
|
| D | sysfs-power | 13 The /sys/power/state file controls system sleep states.
14 Reading from this file returns the available sleep state
21 See Documentation/admin-guide/pm/sleep-states.rst for more
39 See Documentation/admin-guide/pm/sleep-states.rst for more
49 sleep on the next suspend. There are four methods supported:
56 the system will be put to sleep by the platform driver (e.g.
175 system into a sleep state while taking into account the
182 to a sleep state if any wakeup events are reported after the
206 the sleep state represented by that string is queued up. This
209 of whether or not the attempt to put the system to sleep has
[all …]
|
| /Documentation/timers/ |
| D | timers-howto.rst | 2 delays - Information on the various kernel delay / sleep mechanisms
39 You should use the `*sleep[_range]` family of functions.
41 work correctly, using the "right" sleep function will
81 will often sleep longer (~20 ms actual sleep for any
109 TASK_INTERRUPTIBLE before scheduling the sleep. In
110 short, the difference is whether the sleep can be ended
|
| /Documentation/devicetree/bindings/usb/ |
| D | qcom,dwc3.yaml | 84 - sleep:: Sleep clock, used for wakeup when USB3 core goes into low
176 - const: sleep
222 - const: sleep
240 - const: sleep
245 - const: sleep
263 - const: sleep
282 - const: sleep
303 - const: sleep
327 - const: sleep
332 - const: sleep
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | qcom,gcc-msm8994.yaml | 27 - description: Sleep clock source
32 - const: sleep
51 clock-names = "xo", "sleep";
|
| D | qcom,gcc-msm8953.yaml | 26 - description: Sleep clock source
35 - const: sleep
66 "sleep",
|
| /Documentation/admin-guide/perf/ |
| D | meson-ddr-pmu.rst | 59 perf stat -a -e meson_ddr_bw/total_rw_bytes/ -I 1000 sleep 10
67 perf stat -a -e meson_ddr_bw/chan_1_rw_bytes,arm=1/ -I 1000 sleep 10
68 perf stat -a -e meson_ddr_bw/chan_2_rw_bytes,gpu=1/ -I 1000 sleep 10
69 perf stat -a -e meson_ddr_bw/chan_3_rw_bytes,arm=1,gpu=1/ -I 1000 sleep 10
|
| D | thunderx2-pmu.rst | 32 # perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1
38 uncore_dmc_0/write_txns/ sleep 1
44 uncore_l3c_0/inv_hit/ sleep 1
|
| /Documentation/devicetree/bindings/mmc/ |
| D | sdhci-msm.yaml | 84 - description: sleep clock for RCLK delay calibration
92 - enum: [ice, bus, cal, sleep]
93 - enum: [ice, bus, cal, sleep]
94 - enum: [ice, bus, cal, sleep]
95 - enum: [ice, bus, cal, sleep]
111 - const: sleep
119 Should specify sleep pin control groups used for this controller.
|
| /Documentation/scheduler/ |
| D | sched-arch.rst | 38 need_resched is if we are about to sleep the processor until
42 4a. Common problem with this type of sleep appears to be::
48 __asm__("sleep until next interrupt");
58 an interrupt sleep, it needs to be cleared then a memory
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-rockchip.yaml | 80 - const: sleep
82 Names for the pin configuration(s); may be "default" or "sleep",
83 where the "sleep" configuration may describe the state
113 pinctrl-names = "default", "sleep";
|
12345678910>>...14