dwc3: wakeup request details (was: Re: [PATCH 2/2] usb: dwc3: gadget: put link to U0 before Start Transfer)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi John,

Felipe Balbi <felipe.balbi@xxxxxxxxxxxxxxx> writes:
> Synopsys Databook says we should move link to U0
> before issuing a Start Transfer command. We could
> require the gadget driver to call
> usb_gadget_wakeup() however I feel that changing all
> gagdget drivers to keep track of Link State and
> conditionally call usb_gadget_wakeup() would be far
> too much work. For now we will handle this at the
> UDC level, but at some point composite.c should be
> one handling this.
>
> Signed-off-by: Felipe Balbi <felipe.balbi@xxxxxxxxxxxxxxx>

I have been looking at this for a while but I have two question which I
can't seem to answer using Synopsys databook (I have here 2.60a).

i) When is it legal to start Wakeup request ?

ii) What is the proper way to start wakeup request ?

IIRC current code was very much extracted from a BSD reference code
which was sent to me (while back at TI) years ago and now I have been
wondering if current code is actually correct or not. I can't find
answers in the databook. Everytime I look for 'wakeup' on the databook
it's always along the lines of "SW can issue wakeup request" but there's
never a "here's how you start wakeup request and here's when is it legal
to do so" section.

Would you be able to request Synopsys to clarify this in the Databook ?
(I know I'm using an older version of the databook, but I really don't
have anything else right now, sorry).

-- 
balbi

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux