Searched refs:resumed (Results 1 – 21 of 21) sorted by relevance
/Zephyr-latest/drivers/sensor/bosch/bmi323/ |
D | Kconfig | 22 consumption, otherwise it is resumed when initialized. When resumed,
|
/Zephyr-latest/subsys/usb/device_next/ |
D | usbd_class_api.h | 183 if (api->resumed != NULL) { in usbd_class_resumed() 184 api->resumed(c_data); in usbd_class_resumed()
|
/Zephyr-latest/include/zephyr/usb/ |
D | usbh.h | 89 int (*resumed)(struct usbh_contex *const uhs_ctx); member
|
D | usbd.h | 353 void (*resumed)(struct usbd_class_data *const c_data); member
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | comparator.rst | 26 when the comparator is resumed. 31 Comparators are enabled using power management. When resumed, the comparator will actively
|
/Zephyr-latest/tests/drivers/audio/dmic_api/ |
D | README.txt | 16 * Verify that the DMIC can restart sampling after being paused and resumed
|
/Zephyr-latest/drivers/watchdog/ |
D | Kconfig.smartbond | 21 reset at <= -16. Timer can be frozen/resumed using
|
/Zephyr-latest/subsys/pm/ |
D | Kconfig | 81 domain is suspended or resumed. 101 enabled, devices can be suspended or resumed based on the device 127 are resumed.
|
/Zephyr-latest/doc/services/pm/ |
D | device_runtime.rst | 19 not used. On the first device request, it will be resumed and so put into the 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
|
D | device.rst | 86 from a sleep state, devices are resumed in the opposite order that they were 150 state and devices are resumed by the first core that becomes active. 234 * domain this device belongs is resumed.
|
/Zephyr-latest/samples/subsys/usb/shell/ |
D | README.rst | 66 host: USB bus resumed
|
/Zephyr-latest/doc/kernel/services/other/ |
D | float.rst | 153 current FPU user context is saved in the thread object and the ISR is resumed 203 current FPU user context is saved in the thread object and the ISR is resumed
|
/Zephyr-latest/subsys/usb/device_next/class/ |
D | usbd_cdc_ecm.c | 629 .resumed = usbd_cdc_ecm_resumed,
|
D | usbd_hid.c | 662 .resumed = usbd_hid_resumed,
|
D | usbd_cdc_acm.c | 1078 .resumed = usbd_cdc_acm_resumed,
|
D | usbd_cdc_ncm.c | 1180 .resumed = usbd_cdc_ncm_resumed,
|
/Zephyr-latest/doc/ |
D | glossary.rst | 98 reference of their usage and will automatically be suspended or resumed.
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | dfu.rst | 329 resumed, the Distributor will continue sending the firmware from the last successfully transferred
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | lwm2m.rst | 665 - Engine can be resumed by calling :c:func:`lwm2m_engine_resume`.
|
/Zephyr-latest/doc/kernel/services/ |
D | interrupts.rst | 318 will be resumed from low-power state before the ISR is executed, which can be
|
/Zephyr-latest/doc/releases/ |
D | release-notes-3.3.rst | 3351 * :github:`51566` - broken network once lwM2M is resumed after pause
|