0042e1e95f
Short explanation of remote wake up: The device has a possibility to wake up the HOST by sending the wake up request. The request must be previously explicitly enabled by the HOST just before the SUSPEND. The HOST enables the remote wake up functionality by sending SET_FEATURE request with remote wake up flag set to 1. This ususally happens just before the device is suspended. About this PR: When the device decides to wake up the HOST it sends proper request. Nordic USB HW is creating an event when the request has been sent. The Zephyr USB device stack must proerly react to this event and change the state of the device from SUSPENDED. For example if the device was previously in CONFIGURED state it will remain CONFIGURED. For state changes refer to Chapter 9.1.1 form USB 2.0 specification. Signed-off-by: Emil Obalski <emil.obalski@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| Kconfig | ||
| usb_dc_dw.c | ||
| usb_dc_kinetis.c | ||
| usb_dc_mcux_ehci.c | ||
| usb_dc_native_posix.c | ||
| usb_dc_native_posix_adapt.c | ||
| usb_dc_native_posix_adapt.h | ||
| usb_dc_nrfx.c | ||
| usb_dc_sam.c | ||
| usb_dc_sam0.c | ||
| usb_dc_stm32.c | ||
| usb_dw_registers.h | ||