Home
last modified time | relevance | path

Searched full:suspended (Results 1 – 25 of 125) sorted by relevance

12345

/Zephyr-Core-3.5.0/doc/services/pm/
Ddevice_runtime.rst21 state until it is no longer used. At this point, the device will be suspended
45 SUSPENDED [label=PM_DEVICE_STATE_SUSPENDED];
49 init -> SUSPENDED;
50 SUSPENDED -> ACTIVE;
51 ACTIVE -> SUSPENDED;
53 SUSPENDING -> SUSPENDED [constraint=false];
54 SUSPENDED -> SUSPENDING [style=invis];
69 When runtime PM is enabled on a device it will no longer be resumed or suspended
73 determine when a device needs to be resumed or suspended. The API uses the *get*
84 be resumed and suspended on every transaction. In general, it is more
[all …]
Ddevice.rst51 suspended.
78 Devices are suspended only when the last active core is entering a low power
101 SUSPENDED [label=PM_DEVICE_STATE_SUSPENDED];
107 ACTIVE -> SUSPENDING -> SUSPENDED;
108 ACTIVE -> SUSPENDED ["label"="PM_DEVICE_ACTION_SUSPEND"];
109 SUSPENDED -> ACTIVE ["label"="PM_DEVICE_ACTION_RESUME"];
111 {rank = same; SUSPENDED; SUSPENDING;}
113 OFF -> SUSPENDED ["label"="PM_DEVICE_ACTION_TURN_ON"];
114 SUSPENDED -> OFF ["label"="PM_DEVICE_ACTION_TURN_OFF"];
170 * domain this device belongs is suspended.
[all …]
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/
Dblob_srv.rst66 transfer is suspended by the BLOB Transfer Server.
68 The BLOB Transfer Server notifies the user of the suspension by calling the :c:member:`suspended
69 <bt_mesh_blob_srv_cb.suspended>` callback. If the BLOB Transfer Server is in the middle of receiving
72 The BLOB Transfer Client may resume a suspended transfer by starting a new block transfer. The BLOB
87 After a transfer is successfully recovered, the BLOB Transfer Server enters the suspended state. It
88 will stay suspended until the BLOB Transfer Client resumes the transfer, or the user cancels it.
93 will stay suspended until the application calls :c:func:`bt_mesh_blob_srv_cancel`.
/Zephyr-Core-3.5.0/subsys/usb/device/class/
Dbt_h4.c41 static bool suspended; variable
154 suspended = false; in bt_h4_status_cb()
171 suspended = false; in bt_h4_status_cb()
175 suspended = true; in bt_h4_status_cb()
179 if (suspended) { in bt_h4_status_cb()
181 suspended = false; in bt_h4_status_cb()
Dbluetooth.c49 static atomic_t suspended; variable
140 if (atomic_get(&suspended)) { in hci_tx_thread()
147 * as long as device is suspended it should not start in hci_tx_thread()
150 while (atomic_get(&suspended)) { in hci_tx_thread()
315 atomic_clear(&suspended); in bluetooth_status_cb()
333 atomic_clear(&suspended); in bluetooth_status_cb()
336 LOG_DBG("Device suspended"); in bluetooth_status_cb()
337 atomic_set(&suspended, 1); in bluetooth_status_cb()
340 tmp = atomic_clear(&suspended); in bluetooth_status_cb()
/Zephyr-Core-3.5.0/include/zephyr/pm/
Ddevice_runtime.h43 * in #PM_DEVICE_STATE_ACTIVE state, the device will be suspended.
61 * If the device is currently suspended it will be resumed.
76 * This function will resume the device if the device is suspended (usage count
80 * If the device is still being suspended as a result of calling
112 * @retval -EALREADY If device is already suspended (can only happen if get/put
138 * @retval -EALREADY If device is already suspended (can only happen if get/put
/Zephyr-Core-3.5.0/tests/kernel/threads/thread_apis/src/
Dtest_threads_suspend_resume.c116 * If we are suspended, the wakeup should not occur in sleep_suspended()
126 * @details Suspended threads should not wake up unexpectedly if they
127 * happened to have been sleeping when suspended.
142 * has been suspended) in ZTEST()
176 zassert_true(strcmp(str, "suspended") == 0); in ZTEST()
/Zephyr-Core-3.5.0/drivers/dma/
DKconfig.dw_common28 bool "channels should be suspended and drained on stop"
31 Rather than immediately stopping a DMA channel the channel is suspended
/Zephyr-Core-3.5.0/include/zephyr/bluetooth/mesh/
Dblob_srv.h82 /** @brief Transfer suspended callback.
85 * A suspended transfer may resume later from the start of the current
91 * @note The BLOB Transfer Server does not run a timer in the suspended state,
94 * the transfer will be suspended indefinitely, and the BLOB Transfer
99 void (*suspended)(struct bt_mesh_blob_srv *srv); member
103 * Called if the transfer is resumed after being suspended.
/Zephyr-Core-3.5.0/subsys/usb/device_next/
Dusbd_device.h66 * @brief Set device suspended status
69 * @param[in] value new suspended value
74 uds_ctx->status.suspended = value; in usbd_status_suspended()
/Zephyr-Core-3.5.0/tests/subsys/pm/device_wakeup_api/src/
Dmain.c26 * Devices are suspended before SoC on PM_STATE_SUSPEND_TO_RAM, that is why in pm_state_set()
43 * and devices were suspended. in pm_state_set()
105 * enabled, the device will be suspended. This will be in ZTEST()
/Zephyr-Core-3.5.0/tests/net/pm/src/
Dmain.c136 zassert_false(net_if_is_suspended(iface), "net iface is not suspended"); in ZTEST()
151 zassert_true(net_if_is_suspended(iface), "net iface is not suspended"); in ZTEST()
157 zassert_true(net_if_is_suspended(iface), "net iface is not suspended"); in ZTEST()
167 zassert_false(net_if_is_suspended(iface), "net iface is suspended"); in ZTEST()
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/tests_scripts/blob_mdls/
Dblob_srv_persistence.sh33 # Test reaching suspended state and continuation after reboot on new procedure.
65 # Test reaching suspended state and continuation after reboot on new procedure.
Dblob_cli_trans_resume_push.sh7 # Test that BLOB Client can resume a suspended BLOB Transfer in Push mode
Dblob_cli_trans_resume_pull.sh7 # Test that BLOB Client can resume a suspended BLOB Transfer in Pull mode
/Zephyr-Core-3.5.0/tests/subsys/pm/power_domain/src/
Dmain.c141 /* At this point all devices should be SUSPENDED */ in ZTEST()
181 * Now the domain should be suspended since there is no in ZTEST()
194 * With the domain suspended the device state should be OFF, since in ZTEST()
254 /* At this point domain should be SUSPENDED */ in ZTEST()
/Zephyr-Core-3.5.0/subsys/pm/
DKconfig94 domain is suspended or resumed.
114 enabled, devices can be suspended or resumed based on the device
/Zephyr-Core-3.5.0/drivers/sensor/bmi160/
DKconfig61 bool "suspended/not used"
148 bool "suspended/not used"
/Zephyr-Core-3.5.0/samples/philosophers/
DREADME.rst130 …4 Thread 537919712 (Philosopher 1 SUSPENDED PRIO 2) arch_swap (key=key@entry=0) at zephyr/mai…
131 …5 Thread 537919888 (Philosopher 2 SUSPENDED PRIO 1) arch_swap (key=key@entry=0) at zephyr/mai…
132 …6 Thread 537920064 (Philosopher 3 SUSPENDED PRIO 0) arch_swap (key=key@entry=0) at zephyr/mai…
134 …8 Thread 537920416 (Philosopher 5 SUSPENDED PRIO 254) arch_swap (key=key@entry=0) at zephyr/mai…
/Zephyr-Core-3.5.0/dts/bindings/espi/
Dmicrochip,xec-espi-saf.yaml38 description: force suspended erase or program to resume in 32KHz periods
Dmicrochip,xec-espi-saf-v2.yaml44 description: force suspended erase or program to resume in 32KHz periods
/Zephyr-Core-3.5.0/dts/bindings/base/
Dpm.yaml26 suspended or resumed.
/Zephyr-Core-3.5.0/subsys/usb/device/class/hid/
Dcore.c147 bool suspended; member
360 dev_data->suspended = false; in hid_do_status_cb()
387 dev_data->suspended = false; in hid_do_status_cb()
390 LOG_INF("Device suspended"); in hid_do_status_cb()
391 dev_data->suspended = true; in hid_do_status_cb()
395 if (dev_data->suspended) { in hid_do_status_cb()
397 dev_data->suspended = false; in hid_do_status_cb()
698 if (hid_dev_data->configured && !hid_dev_data->suspended) { in hid_int_ep_write()
/Zephyr-Core-3.5.0/include/zephyr/usb/
Dusbh.h86 /** Bus suspended handler */
87 int (*suspended)(struct usbh_contex *const uhs_ctx); member
/Zephyr-Core-3.5.0/drivers/sensor/bmi323/
DKconfig20 runtime management is used, it is initialized into the suspended state,

12345