The corner case for USB remote wakeup

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

 



Hi Alan,

Currently, more and more USB interface 3G modules begin to use at embedded
device, most of them support USB remote wakeup.

According to USB2.0 spec 7.1.7.7 Resume
A device with remote wakeup capability may not generate resume signaling
unless the bus has been continuously in the Idle state for 5 ms (TWTRSM).

That is to say, the remote wakeup featured device may generate resume
signal after 5ms later of USB bus suspend (Full speed J).

Some controllers may have problems if there
is a resume signal on the port as well as the PHY is trying to enter low
power mode. In order to avoid this corner case, the time between set bus suspend 
(portsc.suspendM) and set PHY to low power mode should be within 5ms.
At current EHCI code, only some Intel controllers (has_hostpc) set PHY to low power
mode after bus suspend(but they are also larger than 5ms between bus suspend and
PHY enters low power mode).

My questions are:
- Such resume signal coming and PHY entering low power mode case should be considered
by SoC design(Controller skips resume signal, until PHY has entered low power mode)?
or Software needs to make sure timing (time between set portsc.suspendM and PHY enters
low power mode should less than 5ms)?
- If some controllers already have above concurrency issue, how to work around this?
Is it reasonable to put PHY low power mode interface at EHCI code?

Thanks,
Peter   

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


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

  Powered by Linux