Re: arm64 crash in ffs on 4.9/4.12 - Internal error: Accessing user space memory with fs=KERNEL_DS

On Wed, Aug 30, 2017 at 01:27:32PM -0700, Jerry Zhang wrote: > Hi, > > I'm running into a kernel crash while using the functionfs driver on > 4.9 and 4.12 kernels. This is reproducible by using any of the aio > syscalls with functionfs on the above kernels. The code in question is > in

Re: [PATCH] USB: fix coding style issue

hi Greg > Note, not all subsystems appreciate coding style cleanups, so be aware > of that if you do start to do this type of work outside of > drivers/staging/ Got it. thanks for your friendly reminder. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a

Re: [PATCH v2 3/3] arm64: dts: qcom: Collapse usb support into one node

Quoting Shawn Guo (2017-08-16 23:43:49) > Hi Stephen, > > On Fri, Jul 14, 2017 at 02:40:05PM -0700, Stephen Boyd wrote: > > We currently have three device nodes for the same USB hardware > > block, as evident by the reuse of the same reg address multiple > > times. Now that the chipidea driver

arm64 crash in ffs on 4.9/4.12 - Internal error: Accessing user space memory with fs=KERNEL_DS

Hi, I'm running into a kernel crash while using the functionfs driver on 4.9 and 4.12 kernels. This is reproducible by using any of the aio syscalls with functionfs on the above kernels. The code in question is in ffs_user_copy_worker, which is a work thread that copies a bit of data into

Re: xhci bandwidth problem with isochronous endpoints

On 08/28/2017 06:00 AM, Mathias Nyman wrote: On 19.07.2017 01:39, Curt Meyers wrote: Hello, I have a new USB3 camera that can only operate in isochronous mode. I can open and stream data from the camera using guvcview. The camera has 3 interfaces, two show up as uvc video devices. The

Re: [PATCH] usbip: vhci-hcd: make vhci_hc_driver const

On 08/30/2017 06:52 AM, Bhumika Goyal wrote: > Make this const as it is not modified anywhere. > > Signed-off-by: Bhumika Goyal > --- > drivers/usb/usbip/vhci_hcd.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/usb/usbip/vhci_hcd.c

Re: [PATCH] USB: fix coding style issue

On Wed, Aug 30, 2017 at 09:37:26PM +0800, pierre kuo wrote: > hi Greg: > > 2017-08-16 23:46 GMT+08:00 Greg KH : > > On Wed, Aug 16, 2017 at 11:01:20AM +0800, pierre Kuo wrote: > >> try to fix some codeing style issue, such as "space prohibited" and "not > >> initialise

Re: [PATCH] USB: fix coding style issue

hi Greg: 2017-08-16 23:46 GMT+08:00 Greg KH : > On Wed, Aug 16, 2017 at 11:01:20AM +0800, pierre Kuo wrote: >> try to fix some codeing style issue, such as "space prohibited" and "not >> initialise statics". > > Only do one type of thing in a single patch please. And

[PATCH] usb: imx21-hcd: make imx21_hc_driver const

Make this const as it is not modified anywhere. Signed-off-by: Bhumika Goyal --- drivers/usb/host/imx21-hcd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/host/imx21-hcd.c b/drivers/usb/host/imx21-hcd.c index e25d72e..39ae7fb 100644 ---

[PATCH] usbip: vhci-hcd: make vhci_hc_driver const

Make this const as it is not modified anywhere. Signed-off-by: Bhumika Goyal --- drivers/usb/usbip/vhci_hcd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/usbip/vhci_hcd.c b/drivers/usb/usbip/vhci_hcd.c index c747623..11b9a22 100644 ---

[PATCH v3 1/3] usb: xhci-mtk: add generic compatible string

The xhci-mtk driver is a generic driver for MediaTek xHCI IP, add a generic compatible to avoid confusion when support new SoCs but use a compatible with specific SoC's name "mt8173". Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c |1 + 1 file

[PATCH v3 3/3] dt-bindings: mt8173-mtu3: add generic compatible and rename file

The mt8173-mtu3.txt actually holds the bindings for all mediatek SoCs with usb3 DRD IP, so add a generic compatible and change the name to mediatek,mtu3.txt. Signed-off-by: Chunfeng Yun Acked-by: Rob Herring --- .../usb/{mt8173-mtu3.txt =>

[PATCH v3 2/3] dt-bindings: mt8173-xhci: add generic compatible and rename file

The mt8173-xhci.txt actually holds the bindings for all mediatek SoCs with xHCI controller, so add a generic compatible and change the name to mediatek,mtk-xhci.txt to reflect that. Signed-off-by: Chunfeng Yun --- .../usb/{mt8173-xhci.txt => mediatek,mtk-xhci.txt} |

[PATCH] usb: dwc3: of-simple: Add compatible for Spreadtrum SC9860 platform

Add compatible string to use this generic glue layer to support Spreadtrum SC9860 platform's dwc3 controller. Signed-off-by: Baolin Wang --- drivers/usb/dwc3/dwc3-of-simple.c |1 + 1 file changed, 1 insertion(+) diff --git a/drivers/usb/dwc3/dwc3-of-simple.c

Re: Possible regression between 4.9 and 4.13

On 30/08/2017 11:07, Ard Biesheuvel wrote: > Please don't forget to mention that this is quirky hardware that > depends on BROKEN because it multiplexes MMIO and config space > accesses in the same memory window without any locking whatsoever > (which would be difficult to do in the first place

Re: Possible regression between 4.9 and 4.13

On Wed, Aug 30, 2017 at 10:07:59AM +0100, Ard Biesheuvel wrote: > On 30 August 2017 at 09:55, Mason wrote: > > On 30/08/2017 08:02, Greg Kroah-Hartman wrote: > > > >> To get back to the original issue here, the hardware seems to have died, > >> the driver stops talking to it,

Re: Possible regression between 4.9 and 4.13

On 30 August 2017 at 09:55, Mason wrote: > On 30/08/2017 08:02, Greg Kroah-Hartman wrote: > >> To get back to the original issue here, the hardware seems to have died, >> the driver stops talking to it, and all is good. The "regression" here >> is that we now properly can

Re: Possible regression between 4.9 and 4.13

On Wed, Aug 30, 2017 at 10:55:37AM +0200, Mason wrote: > On 30/08/2017 08:02, Greg Kroah-Hartman wrote: > > > To get back to the original issue here, the hardware seems to have died, > > the driver stops talking to it, and all is good. The "regression" here > > is that we now properly can

[PATCH] usb: host: make ehci_fsl_overrides const and __initconst

Make this structure const as it is not modified. And replace __initdata with __initconst to avoid section conflict error. Signed-off-by: Bhumika Goyal --- drivers/usb/host/ehci-fsl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: Possible regression between 4.9 and 4.13

On 30/08/2017 08:02, Greg Kroah-Hartman wrote: > To get back to the original issue here, the hardware seems to have died, > the driver stops talking to it, and all is good. The "regression" here > is that we now properly can determine that the hardware is crap. Before 4.12, when I unplugged my

Re: [PATCH] USB: serial: option: simplify 3 D-Link device entries

On Tue, Aug 29, 2017 at 04:41:21PM +0200, Johan Hovold wrote: > On Tue, Aug 29, 2017 at 10:45:13AM +0200, Bjørn Mork wrote: > > All the vendor specific interfaces on these devices are serial > > functions handled by this driver, so we can use a single class > > match entry for each. > > > > P:

Re: [PATCH v2] USB: serial: option: add support for D-Link DWM-157 C1

On Tue, Aug 29, 2017 at 09:50:03PM +0200, Maciej S. Szmigiero wrote: > This commit adds support (an ID, really) for D-Link DWM-157 hardware > version C1 USB modem to option driver. > > According to manufacturer-provided Windows INF file the device has four > serial ports: > "D-Link HSPA+DataCard

Re: dwc2: Error message on AMCC 405EX SoC

On Wed, 2017-08-30 at 17:21 +1000, Benjamin Herrenschmidt wrote: > Hi ! > > (Adding the mailing list) > > On the AMCC 405EX SoC, if I enable the OTG, I get this occasional > message: > > dwc2 ef6c.usbotg: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but > reason is unknown > dwc2

dwc2: Error message on AMCC 405EX SoC

Hi ! (Adding the mailing list) On the AMCC 405EX SoC, if I enable the OTG, I get this occasional message: dwc2 ef6c.usbotg: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown dwc2 ef6c.usbotg: hcint 0x0002, intsts 0x04400029 The core version is: dwc2

Re: Possible regression between 4.9 and 4.13

On Wed, Aug 30, 2017 at 08:36:23AM +0200, Lukas Wunner wrote: > On Tue, Aug 29, 2017 at 05:51:38PM +0200, Greg Kroah-Hartman wrote: > > On Tue, Aug 29, 2017 at 05:34:56PM +0200, Lukas Wunner wrote: > > > On Tue, Aug 29, 2017 at 04:47:25PM +0200, Greg Kroah-Hartman wrote: > > > > On Tue, Aug 29,

Re: Possible regression between 4.9 and 4.13

On Tue, Aug 29, 2017 at 05:51:38PM +0200, Greg Kroah-Hartman wrote: > On Tue, Aug 29, 2017 at 05:34:56PM +0200, Lukas Wunner wrote: > > On Tue, Aug 29, 2017 at 04:47:25PM +0200, Greg Kroah-Hartman wrote: > > > On Tue, Aug 29, 2017 at 03:38:52PM +0200, Lukas Wunner wrote: > > Is 0x not a

Re: Possible regression between 4.9 and 4.13

On Wed, Aug 30, 2017 at 01:53:10AM +0200, Lukas Wunner wrote: > On Tue, Aug 29, 2017 at 04:28:53PM +0300, Mathias Nyman wrote: > > This tight check was originally done to detect pci hotplug removed > > hosts as soon as possible. > > In Mason's case, the parent of the XHCI controller isn't a