On Mon, Jul 20, 2015 at 2:53 PM, Felipe Balbi wrote:
> On Mon, Jul 20, 2015 at 02:39:58PM -0500, Bin Liu wrote:
>> On Mon, Jul 20, 2015 at 2:10 PM, Felipe Balbi wrote:
>> > On Mon, Jul 20, 2015 at 02:02:30PM -0500, Bin Liu wrote:
>> >> Hi,
>> >>
>> >> I was trying to understand how remote wakeup
On Mon, Jul 20, 2015 at 02:39:58PM -0500, Bin Liu wrote:
> On Mon, Jul 20, 2015 at 2:10 PM, Felipe Balbi wrote:
> > On Mon, Jul 20, 2015 at 02:02:30PM -0500, Bin Liu wrote:
> >> Hi,
> >>
> >> I was trying to understand how remote wakeup works in the gadget framework.
> >>
> >> It seems most UDC dr
On Mon, Jul 20, 2015 at 2:10 PM, Felipe Balbi wrote:
> On Mon, Jul 20, 2015 at 02:02:30PM -0500, Bin Liu wrote:
>> Hi,
>>
>> I was trying to understand how remote wakeup works in the gadget framework.
>>
>> It seems most UDC drivers define .wakeup() call, which is invoked by
>> usb_gadget_wakeup()
On Mon, Jul 20, 2015 at 02:02:30PM -0500, Bin Liu wrote:
> Hi,
>
> I was trying to understand how remote wakeup works in the gadget framework.
>
> It seems most UDC drivers define .wakeup() call, which is invoked by
> usb_gadget_wakeup() wrapper. But none of the gadget drivers (except
> g_zero) c
Hi,
I was trying to understand how remote wakeup works in the gadget framework.
It seems most UDC drivers define .wakeup() call, which is invoked by
usb_gadget_wakeup() wrapper. But none of the gadget drivers (except
g_zero) calls it. Does it mean the gadget framework does not support
remote wake
