(resending in plain text) Hello all, thank you for all your information. It has been very helpful. I was able to implement the usb_gadget_wakeup() call and set the USB_CONFIG_ATT_WAKEUP bit. Setting the bit did create the /sys/bus/usb/devices/.../power wakeup files that I noticed were missing. Unfortunately usb_gadget_wakeup() calls gadget->ops functions to send the signal and these need to be implemented as well. From my understanding I need to translate the __dwc3_gadget_wakeup() function in linux/drivers/usb/dwc3/gadget.c into raw_gadget.c. I have not been able to properly look through the __dwc3_gadget_wakeup() function yet, Andrey is it feasible to write that function in the raw_gadget currently or is there something else I am missing where I do not need that ops function in raw_gadget? On Fri, Jun 28, 2024 at 9:19 PM Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > On Fri, Jun 28, 2024 at 09:11:39PM +0000, Thinh Nguyen wrote: > > Hi Alan, > > > > On Fri, Jun 28, 2024, Alan Stern wrote: > > > > > > While the wakeup_capable and wakeup_armed bitflags are defined in > > > linux/usb/gadget.h, it doesn't look like any of the UDC drivers > > > implement them. So it may not be possible to see whether the UDC > > > supports remote wakeup (but it appears that most of them do). > > > > > > > The dwc3 driver handles those bitflags. > > I stand corrected; I should have said that none of the UDC drivers in > drivers/usb/gadget/udc implements the flags. > > Alan Stern -- -Thanks, Darrion