mbox series

[v2,0/3] xhci fixes for usb-linus

Message ID 1537458202-438-1-git-send-email-mathias.nyman@linux.intel.com (mailing list archive)
Headers show
Series xhci fixes for usb-linus | expand

Message

Mathias Nyman Sept. 20, 2018, 3:43 p.m. UTC
Hi Greg

Second try, shuffling patches between for-usb-linus and for-usb-next

A few patches that makes sure USB3 devices enumerate to correct speed
after resume on Mediatek hosts, enables role mux on Apollo lake platforms,
and adds the missing cold attach status (CAS) bit quirk to Intel Sunrise
Point xhci controllers.

Changes since v1

- Moved following patches from this series to for-usb-next (4.20)
  xhci: Avoid USB autosuspend when resuming USB2 ports.
  usb: xhci: tegra: Firmware header is little endian

- Added patches to this series from for-usb-next queue:
  usb: xhci-mtk: resume USB3 roothub first
  usb: typec: pci: Enable Intel USB role mux on Apollo Lake platforms

- Added stable tags

Chunfeng Yun (1):
  usb: xhci-mtk: resume USB3 roothub first

Heikki Krogerus (1):
  usb: typec: pci: Enable Intel USB role mux on Apollo Lake platforms

Mathias Nyman (1):
  xhci: Add missing CAS workaround for Intel Sunrise Point xHCI

 drivers/usb/host/xhci-mtk.c | 4 ++--
 drivers/usb/host/xhci-pci.c | 8 ++++++--
 2 files changed, 8 insertions(+), 4 deletions(-)

Comments

Greg KH Sept. 28, 2018, 12:51 p.m. UTC | #1
On Thu, Sep 20, 2018 at 06:43:19PM +0300, Mathias Nyman wrote:
> Hi Greg
> 
> Second try, shuffling patches between for-usb-linus and for-usb-next
> 
> A few patches that makes sure USB3 devices enumerate to correct speed
> after resume on Mediatek hosts, enables role mux on Apollo lake platforms,
> and adds the missing cold attach status (CAS) bit quirk to Intel Sunrise
> Point xhci controllers.
> 
> Changes since v1
> 
> - Moved following patches from this series to for-usb-next (4.20)
>   xhci: Avoid USB autosuspend when resuming USB2 ports.
>   usb: xhci: tegra: Firmware header is little endian
> 
> - Added patches to this series from for-usb-next queue:
>   usb: xhci-mtk: resume USB3 roothub first
>   usb: typec: pci: Enable Intel USB role mux on Apollo Lake platforms
> 
> - Added stable tags
> 
> Chunfeng Yun (1):
>   usb: xhci-mtk: resume USB3 roothub first
> 
> Heikki Krogerus (1):
>   usb: typec: pci: Enable Intel USB role mux on Apollo Lake platforms
> 
> Mathias Nyman (1):
>   xhci: Add missing CAS workaround for Intel Sunrise Point xHCI
> 
>  drivers/usb/host/xhci-mtk.c | 4 ++--
>  drivers/usb/host/xhci-pci.c | 8 ++++++--
>  2 files changed, 8 insertions(+), 4 deletions(-)

I only received 2 patches here, not 3, am I missing something on my end?

Can you resend all of these again?

sorry,

greg k-h
Mathias Nyman Oct. 1, 2018, 3:35 p.m. UTC | #2
On 28.09.2018 15:51, Greg KH wrote:
> On Thu, Sep 20, 2018 at 06:43:19PM +0300, Mathias Nyman wrote:
>> Hi Greg
>>
>> Second try, shuffling patches between for-usb-linus and for-usb-next
>>
>> A few patches that makes sure USB3 devices enumerate to correct speed
>> after resume on Mediatek hosts, enables role mux on Apollo lake platforms,
>> and adds the missing cold attach status (CAS) bit quirk to Intel Sunrise
>> Point xhci controllers.
>>
>> Changes since v1
>>
>> - Moved following patches from this series to for-usb-next (4.20)
>>    xhci: Avoid USB autosuspend when resuming USB2 ports.
>>    usb: xhci: tegra: Firmware header is little endian
>>
>> - Added patches to this series from for-usb-next queue:
>>    usb: xhci-mtk: resume USB3 roothub first
>>    usb: typec: pci: Enable Intel USB role mux on Apollo Lake platforms
>>
>> - Added stable tags
>>
>> Chunfeng Yun (1):
>>    usb: xhci-mtk: resume USB3 roothub first
>>
>> Heikki Krogerus (1):
>>    usb: typec: pci: Enable Intel USB role mux on Apollo Lake platforms
>>
>> Mathias Nyman (1):
>>    xhci: Add missing CAS workaround for Intel Sunrise Point xHCI
>>
>>   drivers/usb/host/xhci-mtk.c | 4 ++--
>>   drivers/usb/host/xhci-pci.c | 8 ++++++--
>>   2 files changed, 8 insertions(+), 4 deletions(-)
> 
> I only received 2 patches here, not 3, am I missing something on my end?
> 
> Can you resend all of these again?
> 

Sure, resending

-Mathias