Re: [PATCH 01/10] usb: xhci-mtk: resume USB3 roothub first

On 14.09.2018 16:27, Greg KH wrote: On Thu, Sep 13, 2018 at 03:23:54PM +0300, Mathias Nyman wrote: From: Chunfeng Yun Give USB3 devices a better chance to enumerate at USB3 speeds if they are connected to a suspended host. Porting from "671ffdff5b13 xhci: resume USB 3 roothub first" Signed-of

Re: [PATCH 3/3] xhci: Add missing CAS workaround for Intel Sunrise Point xHCI

On 14.09.2018 16:01, Greg KH wrote: On Fri, Sep 14, 2018 at 03:33:31PM +0300, Mathias Nyman wrote: The workaround for missing CAS bit is also needed for xHC on Intel sunrisepoint PCH. For more details see: Intel 100/c230 series PCH specification update Doc #332692-006 Errata #8 Signed-off-by:

Re: [PATCH 07/10] usb: typec: pci: Enable Intel USB role mux on Apollo Lake platforms

On 14.09.2018 16:27, Greg KH wrote: On Thu, Sep 13, 2018 at 03:24:00PM +0300, Mathias Nyman wrote: From: Heikki Krogerus Intel Apollo Lake has the same internal USB role mux as Intel Cherry Trail. Signed-off-by: Heikki Krogerus Signed-off-by: Mathias Nyman --- drivers/usb/host/xhci-pci.c

Re: [PATCH 2/3] xhci: Avoid USB autosuspend when resuming USB2 ports.

On 14.09.2018 16:00, Greg KH wrote: On Fri, Sep 14, 2018 at 03:33:30PM +0300, Mathias Nyman wrote: From: Anshuman Gupta When USB bus host controller root hub resumes from autosuspend, it immediately tries to enter auto-suspend, but there can be a scenario when root hub is resuming its usb2 por

Re: How to be notified of endpoint requests when writing a userspace gadget driver?

On Sat, 15 Sep 2018, Alistair Buxton wrote: > On 15 September 2018 at 21:11, Alan Stern wrote: > > On Sat, 15 Sep 2018, Alistair Buxton wrote: > > > Wrong -- bInterval is a maximum value only and the host is free to poll > > more quickly. > > I can only say that real world testing contradicts t

[PATCH 0/1] musb fixes for v4.19-rc5

Hi Greg, Here is one musb fix for v4.19 rc, which fixes the interfering issue among the two musb controllers in dsps glue driver. Please let me know if any change is needed. Regards, -Bin. --- Bin Liu (1): usb: musb: dsps: do not disable CPPI41 irq in driver teardown drivers/usb/musb/musb_ds

[PATCH 1/1] usb: musb: dsps: do not disable CPPI41 irq in driver teardown

TI AM335x CPPI 4.1 module uses a single register bit for CPPI interrupts in both musb controllers. So disabling the CPPI irq in one musb driver breaks the other musb module. Since musb is already disabled before tearing down dma controller in musb_remove(), it is safe to not disable CPPI irq in mu

Re: [PATCH] usb: core: safely deal with the dynamic quirk lists

at 16:58, Harry Pan wrote: Applying dynamic usbcore quirks in early booting when the slab is not yet ready would cause kernel panic of null pointer dereference because the quirk_count has been counted as 1 while the quirk_list was failed to allocate. i.e., [1.044970] BUG: unable to handle

Re: [PATCH 1/5] misc: rtsx_usb: Use USB remote wakeup signaling for card insertion detection

at 21:41, Alan Stern wrote: On Thu, 13 Sep 2018, Kai-Heng Feng wrote: I am working on the next version of this series, and the last missing puzzle is to differentiate system-wide resume from runtime resume in usb_driver's resume() and reset_resume() callback. The parent device, rtsx_usb, has

Re: [PATCH v2 05/17] compat_ioctl: move more drivers to generic_compat_ioctl_ptrarg

On Wed, 12 Sep 2018 17:08:52 +0200 Arnd Bergmann wrote: > The .ioctl and .compat_ioctl file operations have the same prototype so > they can both point to the same function, which works great almost all > the time when all the commands are compatible. > > One exception is the s390 architecture,

Re: [PATCH] net: usb: remove redundant null pointer check before of_node_put

From: zhong jiang Date: Sun, 16 Sep 2018 21:20:17 +0800 > of_node_put has taken the null pointer check into account. So it is > safe to remove the duplicated check before of_node_put. > > Signed-off-by: zhong jiang Applied.

[PATCH net,stable] qmi_wwan: set DTR for modems in forced USB2 mode

Recent firmware revisions have added the ability to force these modems to USB2 mode, hiding their SuperSpeed capabilities from the host. The driver has been using the SuperSpeed capability, as shown by the bcdUSB field of the device descriptor, to detect the need to enable the DTR quirk. This met

RE: [PATCH net,stable] qmi_wwan: set DTR for modems in forced USB2 mode

Many thanks Bjørn! -Original Message- From: Bjørn Mork Sent: Monday, September 17, 2018 13:00 To: net...@vger.kernel.org Cc: linux-usb@vger.kernel.org; Fred Veldini ; Deshu Wen ; Bjørn Mork Subject: [PATCH net,stable] qmi_wwan: set DTR for modems in forced USB2 mode Recent firmware re

Re: [PATCH net,stable] qmi_wwan: set DTR for modems in forced USB2 mode

From: Bjørn Mork Date: Mon, 17 Sep 2018 22:00:24 +0200 > Recent firmware revisions have added the ability to force > these modems to USB2 mode, hiding their SuperSpeed > capabilities from the host. The driver has been using the > SuperSpeed capability, as shown by the bcdUSB field of the > devic

[PATCH] usb: phy: mxs: fix spelling mistake "stardard" -> "standard"

From: Colin Ian King Trivial fix to spelling mistake in dev_dbg message Signed-off-by: Colin Ian King --- drivers/usb/phy/phy-mxs-usb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-usb.c index e5aa24c1e4fd..1b1bb0ad