Re: Runtime PM enabled USB port no longer responses to hotplug after commit dec08194ff

2017-08-14 Thread Mathias Nyman

On 11.08.2017 19:01, Kai-Heng Feng wrote:

Hi,

My ASUS PRIME B350M-A uses this XHCI chip:

03:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] USB
3.1 XHCI Controller [1022:43bb] (rev 02)

...which matches to the PCI_DEVICE_ID_AMD_PROMONTORYA_2.

Revert commit dec08194ffeccfa1cf085906b53d301930eae18f ("xhci: Limit
USB2 port wake support for AMD Promontory hosts") can solve the
regression.

Now both front panel USB ports stop responding to hotplug events now.
Is it an overkill to disable all wake up bits?



I was concerned this patch could cause issues for AMD Promontory users.

Adding more people who were involved with this.

Having BIOS disabled USB2 ports waking up at hotplug seem like a
much smaller issue than USB2 ports not waking up at all.

Any comments from people involved with AMD promontory?

If we can't find a different solution we might need to revert this one.

reference to previous discussion:
http://marc.info/?l=linux-usb=149674402028177=2

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


Runtime PM enabled USB port no longer responses to hotplug after commit dec08194ff

2017-08-11 Thread Kai-Heng Feng
Hi,

My ASUS PRIME B350M-A uses this XHCI chip:

03:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] USB
3.1 XHCI Controller [1022:43bb] (rev 02)

...which matches to the PCI_DEVICE_ID_AMD_PROMONTORYA_2.

Revert commit dec08194ffeccfa1cf085906b53d301930eae18f ("xhci: Limit
USB2 port wake support for AMD Promontory hosts") can solve the
regression.

Now both front panel USB ports stop responding to hotplug events now.
Is it an overkill to disable all wake up bits?

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