Hi, Jun Li <jun.li@xxxxxxx> writes: >> >> Hi Thinh, could you comment this? >> > >> > You only need to wake up the usb2 phy when issuing the command while >> > running in highspeed or below. If you're running in SS or higher, >> > internally the controller does it for you for usb3 phy. In Jun's case, >> > it seems like it takes longer for his phy to wake up. >> > >> > IMO, in this case, I think it's fine to increase the command timeout. >> >> Is there an upper limit to this? Is 32k clock the slowest that can be fed to the >> PHY as a suspend clock? > > Yes, 32K clock is the slowest, Per DWC3 document on Power Down Scale > (bits 31:19 of GCTL): > > "Power Down Scale (PwrDnScale) > The USB3 suspend_clk input replaces pipe3_rx_pclk as a clock source > to a small part of the USB3 controller that operates when the SS PHY > is in its lowest power (P3) state, and therefore does not provide a clock. > The Power Down Scale field specifies how many suspend_clk periods > fit into a 16 kHz clock period. When performing the division, round up > the remainder. > For example, when using an 8-bit/16-bit/32-bit PHY and 25-MHz Suspend clock, > Power Down Scale = 25000 kHz/16 kHz = 13'd1563 (rounder up) > Note: > - Minimum Suspend clock frequency is 32 kHz > - Maximum Suspend clock frequency is 125 MHz" Cool, now do we have an upper bound for how many clock cycles it takes to wake up the PHY? Then we can just set the time to that upper bound. -- balbi
Attachment:
signature.asc
Description: PGP signature
