| /Zephyr-latest/dts/bindings/power/ |
| D | zephyr,power-state.yaml | 16 - "suspend-to-idle"
18 - "suspend-to-ram"
19 - "suspend-to-disk"
38 the power management subsystem will not suspend devices before entering
|
| /Zephyr-latest/subsys/pm/ |
| D | Kconfig | 37 bool "Suspend-to-RAM (S2RAM)"
40 This option enables suspend-to-RAM (S2RAM).
46 By default a magic word in RAM is used to mark entering suspend-to-RAM. Enabling
106 bool "[DEPRECATED] Use only on Runtime Power Management on system suspend / resume"
109 On system suspend / resume do not trigger the Device PM hooks but
124 management. The power management subsystem will suspend
|
| /Zephyr-latest/samples/boards/st/power_mgmt/suspend_to_ram/ |
| D | README.rst | 2 :name: Suspend to RAM
5 Use suspend to RAM low power mode on STM32.
13 SPI loopback is also available but not yet implemented for Suspend To RAM PM
16 .. _stm32-pm-suspend-to-ram-sample-requirements:
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/classic/ |
| D | a2dp.rst | 17 * Source or Sink suspend the media. using :code:`a2dp suspend`.
63 uart:~$ a2dp suspend
64 success to suspend
96 <after a2dp suspend of source side>
97 receive requesting suspend and accept
|
| /Zephyr-latest/include/zephyr/arch/common/ |
| D | pm_s2ram.h | 42 * @brief Save CPU context on suspend
44 * This function is used on suspend-to-RAM (S2RAM) to save the CPU context in
61 * @brief Mark that core is entering suspend-to-RAM state.
77 * @brief Check suspend-to-RAM marking and clear its state.
79 * Function is used to determine if resuming after suspend-to-RAM shall be performed
90 * @retval true if marking is found which indicates resuming after suspend-to-RAM.
|
| /Zephyr-latest/tests/kernel/threads/thread_apis/src/ |
| D | test_threads_suspend_resume.c | 30 /* checkpoint: suspend current thread */ in threads_suspend_resume()
33 /* checkpoint: created thread shouldn't be executed after suspend */ in threads_suspend_resume()
45 * @brief Check the suspend and resume functionality in
49 * thread which is cooperative and suspend it, make sure it doesn't
61 * @brief Check the suspend and resume functionality in
65 * thread which is preemptive and suspend it, make sure it doesn't gets
173 /* suspend created thread */ in ZTEST()
178 /* Resume an suspend thread will make it to be next eligible.*/ in ZTEST()
|
| /Zephyr-latest/include/zephyr/pm/ |
| D | state.h | 48 * @brief Suspend to idle state
50 * The system goes through a normal platform suspend where it puts
64 * saved relative to suspend to idle, but the resume latency will
66 * state with suspend to idle state on uniprocessor system.
72 * @brief Suspend to ram state
84 * @brief Suspend to disk state
91 * went to suspend to disk.
126 * power-state-name = "suspend-to-idle";
133 * power-state-name = "suspend-to-idle";
148 * will suspend devices before entering this state and will
[all …]
|
| /Zephyr-latest/tests/subsys/pm/power_states_api/boards/ |
| D | native_sim.overlay | 16 power-state-name = "suspend-to-idle";
30 power-state-name = "suspend-to-ram";
37 power-state-name = "suspend-to-disk";
|
| /Zephyr-latest/boards/shields/g1120b0mipi/boards/ |
| D | mimxrt595_evk_mimxrt595s_cm33.overlay | 7 /* Change deep sleep config for suspend mode to keep SMARTDMA ram powered,
10 &suspend {
|
| /Zephyr-latest/dts/bindings/pwm/ |
| D | microchip,xec-pwmbbled.yaml | 53 When BBLED enter into Suspend state, 48MHz clock will be switched off by
55 There may be a product requirement, either to blink (or) not blink LED in Suspend state.
57 the LED in Suspend state.
|
| /Zephyr-latest/tests/subsys/pm/device_runtime_api/src/ |
| D | main.c | 26 /* make sure we test blocking path (suspend is ongoing) */ in get_runner()
87 * - get + asynchronous put + get (while suspend still ongoing)
113 /* usage: 2, -1, suspend: no */ in ZTEST()
120 /* usage: 1, -1, suspend: yes */ in ZTEST()
128 /* usage: 0, -1, suspend: no (unbalanced call) */ in ZTEST()
145 /* usage: 1, -1, suspend: yes (queued) */ in ZTEST()
159 /* usage: 0, -1, suspend: no (unbalanced call) */ in ZTEST()
163 /* usage: 0, -1, suspend: no (unbalanced call) */ in ZTEST()
175 /*** get + asynchronous put + get (while suspend still ongoing) ***/ in ZTEST()
186 /* usage: 1, -1, suspend: yes (queued) */ in ZTEST()
[all …]
|
| /Zephyr-latest/tests/subsys/pm/power_states_api/src/ |
| D | main.c | 84 /** Lets sleep long enough to suspend the CPU with `suspend to ram` in ZTEST()
90 zassert_true(suspend_to_ram_count == 0, "Invalid suspend to ram count"); in ZTEST()
93 * the cpu will suspend to ram. in ZTEST()
|
| /Zephyr-latest/soc/nordic/nrf54h/ |
| D | pm_s2ram.h | 14 * @brief Save CPU state on suspend
16 * This function is used on suspend-to-RAM (S2RAM) to save the CPU state in
|
| /Zephyr-latest/samples/subsys/pm/latency/boards/ |
| D | native_sim.overlay | 14 suspend_to_idle: suspend-to-idle {
16 power-state-name = "suspend-to-idle";
|
| /Zephyr-latest/doc/services/pm/ |
| D | device_runtime.rst | 14 This information is used to determine when to suspend or resume a device based
61 when they do not. Therefore, applications can not manually suspend or resume a
95 suspend the device if necessary. It is worth to note that in both cases, the
110 the suspend operation, again, if device is no longer used. The suspension will
122 by the PM subsystem to suspend or resume devices.
131 /* suspend the device */
150 function will suspend the device if its state is
208 In case the suspend operation is *slow*, the device driver can use the
226 /* "put" device (decreases usage count, schedule suspend if no more users) */
|
| D | device.rst | 26 devices, the decision to suspend or resume a device can also be
32 to suspend or resume a device.
36 put devices into low-power states (suspend) when they are not in
45 when to suspend or resume devices. For example, a networking
83 management and then suspend devices before changing state. The subsystem takes
108 power-state-name = "suspend-to-ram";
224 /* suspend the device */
271 uart:~$ pm suspend buttons
289 suspend and resume actions and it's currently active, ``buttons`` supports
298 subsystem can suspend devices, as described in :ref:`pm-device-system-pm`. This
[all …]
|
| /Zephyr-latest/tests/subsys/pm/policy_api/ |
| D | app.overlay | 26 power-state-name = "suspend-to-ram";
34 power-state-name = "suspend-to-ram";
|
| /Zephyr-latest/soc/infineon/cat1b/cyw20829/ |
| D | power.c | 32 LOG_DBG("Entering PM state suspend to idle"); in pm_state_set()
36 LOG_DBG("Entering PM state suspend to RAM"); in pm_state_set()
|
| /Zephyr-latest/subsys/net/lib/shell/ |
| D | suspend.c | 57 SHELL_SUBCMD_ADD((net), suspend, NULL,
58 "Suspend a network interface",
|
| /Zephyr-latest/tests/benchmarks/thread_metric/src/ |
| D | tm_preemptive_scheduling_test.c | 118 * self-suspend. in tm_preemptive_thread_0_entry()
140 * self-suspend. in tm_preemptive_thread_1_entry()
146 /* Suspend self! */ in tm_preemptive_thread_1_entry()
165 * self-suspend. in tm_preemptive_thread_2_entry()
171 /* Suspend self! */ in tm_preemptive_thread_2_entry()
196 /* Suspend self! */ in tm_preemptive_thread_3_entry()
213 /* Self suspend thread 4. */ in tm_preemptive_thread_4_entry()
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.5.rst | 56 - Added suspend/resume to QMSI drivers.
132 * ``ZEP-226`` - Update sample PMA to support device suspend/resume
170 * ``ZEP-512`` - Add suspend/resume support for some core devices to enable Deep Sleep support in PMA
178 * ``ZEP-652`` - QMSI shim driver: RTC: Implement suspend and resume callbacks
179 * ``ZEP-655`` - QMSI shim driver: PWM: Implement suspend and resume callbacks
180 * ``ZEP-658`` - QMSI shim driver: GPIO: Implement suspend and resume callbacks
181 * ``ZEP-659`` - QMSI shim driver: UART: Implement suspend and resume callbacks
182 * ``ZEP-662`` - QMSI shim driver: Pinmux: Implement suspend and resume callbacks
189 * ``ZEP-305`` - Device Suspend / Resume infrastructure
|
| /Zephyr-latest/tests/kernel/smp_suspend/ |
| D | Kconfig | 4 mainmenu "SMP suspend test"
|
| /Zephyr-latest/tests/subsys/pm/power_mgmt/src/ |
| D | main.c | 20 /* for checking power suspend and resume order between system and devices */
57 * The power management subsystem uses this order to suspend and resume
214 "Notification to enter suspend was not sent to the App"); in pm_state_set()
276 /* enter suspend */ in notify_pm_state_entry()
278 "Notification to enter suspend was not sent to the App"); in notify_pm_state_entry()
301 /* leave suspend */ in notify_pm_state_exit()
303 "Notification to leave suspend was not sent to the App"); in notify_pm_state_exit()
319 * - The idle routine provide a timeout parameter to the suspend routine
|
| /Zephyr-latest/dts/arm/microchip/ |
| D | mec172xnsz.dtsi | 35 power-state-name = "suspend-to-idle";
41 power-state-name = "suspend-to-ram";
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/src/ |
| D | test_advertiser.c | 602 bool suspend; member
613 LOG_DBG("end(): err (%d), suspend (%d), i (%d)", err, adv_data->suspend, in adv_send_end()
618 if (adv_data->suspend) { in adv_send_end()
634 LOG_DBG("start(): err (%d), suspend (%d), i (%d)", err, adv_data->suspend, in adv_send_start()
637 if (adv_data->suspend) { in adv_send_start()
657 static void adv_create_and_send(bool suspend, uint8_t first_byte, struct adv_suspend_ctx *adv_data) in adv_create_and_send() argument
666 adv_data[i].suspend = suspend; in adv_create_and_send()
692 /* Fill up the adv pool and suspend the advertiser in the first start callback call. */ in test_tx_disable()
704 /* Fill up the adv pool and suspend the advertiser and let it send all advs. */ in test_tx_disable()
|
