On 03/14/2013 05:42 PM, Alexis R. Cortes wrote:
Hi Sarah,
On 3/11/2013 5:20 PM, Sarah Sharp wrote:
On Mon, Mar 11, 2013 at 05:33:26PM +0000, Cortes, Alexis wrote:
Hi Sarah,
Sorry for my delayed response, I was investigating this. By 'Inactive' state you mean the Compliance mode? since SS.Inactive and Compliance are not the same.
Yes, I mean Compliance mode.
When in D3hot or D3cold, the host must be able to transmit a PME whenever a device is plugged into the DS port. If a SS device is plugged into DS port and fails to make it to U0, the Port will land in Compliance or SS.Disabled. If Compliance, then there will be no PME notification. If it lands in SS.Disabled, the USB2 will be enabled and then a PME notification will be sent for USB2 connection. I just realized this.
Then we definitely need to poll during runtime suspend, or disable
runtime PM for the PCI device all together.
Does this mean wake from S3 (system suspend) on device connect will be
broken as well, if the port fails to make it to U0 and goes into
Compliance mode?
I believe so, since the timing issues caused by the hardware could make
the port enter to Compliance, thus it will never reach U0. However I
have never tested this scenario.
Best Regards,
Alexis Cortes.
Alexis,
Does this mean that systems having this chip should not use hibernate/suspend?
--
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
