Regression - Linux 4.9: ums_eneub6250 broken: transfer buffer not dma capable - Trace

Hello! Since Linux 4.9, ums_eneub6250 is broken. It's working fine if CONFIG_VMAP_STACK is disabled. I would be glad if it would be fixed. Thanks, kind regards, Andreas Apr 15 17:58:54 notebook2 kernel: usb 1-1.1: new high-speed USB device number 3 using ehci-pci Apr 15 17:58:54 notebook2

Re: [PATCH v4 6/6] sound: replace /proc/bus/usb by /dev/bus/usb

On Mon, 17 Apr 2017 02:51:11 +0200, Mauro Carvalho Chehab wrote: > > The /proc/bus/usb devices don't exist anymore, since when we > got rid of usbfs. Those devices are now seen at > /dev/bus/usb. > > Signed-off-by: Mauro Carvalho Chehab Since it's a driver fix, I

Re: usb: host: xhci: stalled endpoint ring not cleared on empty td_list

On Sun, 16 Apr 2017, Rolf Evers-Fischer wrote: > Hi Chris, > > On 04/11/2017 04:33 PM, Christian Gromm wrote: > > Well, this sounds like a workaround to me as you are changing the timing > > by waiting for the URBs to finish. This might prevent the > > race from happening. > > > I personally

Re: [PATCH] usb: gadget: remove redundant self assignment

On Sun, Apr 16, 2017 at 08:12:50PM -0700, Stefan Agner wrote: > The assignment ret = ret is redundant and can be removed. > > Signed-off-by: Stefan Agner > --- > A very similar patch has been applied already last year, but there is > a second such assignment... > > -- > Stefan

[PATCH 1/1] usb: host: xhci-ring: don't need to clear interrupt pending for MSI enabled hcd

According to xHCI spec Figure 30: Interrupt Throttle Flow Diagram If PCI Message Signaled Interrupts (MSI or MSI-X) are enabled, then the assertion of the Interrupt Pending (IP) flag in Figure 30 generates a PCI Dword write. The IP flag is automatically cleared by

Re: [PATCH v2 2/2] usb: dwc2: add multiple clocks handling

Hi John, I apologize if this was presumptuous, would you like to have a look this series please? On 2017/3/28 21:49, Felipe Balbi wrote: Hi, Heiko Stübner writes: Am Donnerstag, 9. Februar 2017, 10:44:39 CET schrieb Frank Wang: Since dwc2 may have one or more input

[PATCH V2] USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit

This development kit has an FT4232 on it with a custom USB VID/PID. The FT4232 provides four UARTs, but only two are used. The UART 0 is used by the FlashPro5 programmer and UART 2 is connected to the SmartFusion2 CortexM3 SoC UART port. Note that the USB VID is registered to Actel according to

Re: usb: dwc2: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 146s

Hi, > Stefan Wahren hat am 31. Oktober 2016 um 21:34 > geschrieben: > > > I inspired by this issue [1] i build up a slightly modified setup with a > Raspberry Pi B (mainline kernel 4.9rc3), a powered 7 port USB hub and 5 > Prolific > PL2303 USB to serial convertors. I

Re: [PATCH] USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit

On 02/13/2017 10:29 AM, Johan Hovold wrote: > [+CC: linux-usb] > > Always make sure to CC linux-usb for USB patches. > > On Fri, Feb 10, 2017 at 05:16:12PM +0100, Marek Vasut wrote: >> This development kit has an FT4232 on it with a custom USB VID/PID. >> The FT4232 provides four UARTs, but only

[GIT PULL] usb: chipidea changes for v4.12-rc1

The following changes since commit 4495c08e84729385774601b5146d51d9e5849f81: Linux 4.11-rc2 (2017-03-12 14:47:08 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb.git/ tags/usb-ci-v4.12-rc1 for you to fetch changes up to

Re: Ops in usb stack

On 2017-04-18 02:06, Anders Eriksson wrote: [1.056684] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) The pesky dwc_otg driver is the reason for your problem, it is not part of the official 4.9 kernel. It was replaced by dwc2 some two years ago. /Lars -- To unsubscribe from this

[PATCH] usb: dwc3: add disable u2mac linestate check quirk

This patch adds a quirk to disable USB 2.0 MAC linestate check during HS transmit. Refer the dwc3 databook, we can use it for some special platforms if the linestate not reflect the expected line state(J) during transmission. When use this quirk, the controller implements a fixed 40-bit

Re: Regression - Linux 4.9: ums_eneub6250 broken: transfer buffer not dma capable - Trace

On Mon, 17 Apr 2017, Greg KH wrote: > On Mon, Apr 17, 2017 at 11:28:44AM +0200, Andreas Hartmann wrote: > > Hello! > > > > Since Linux 4.9, ums_eneub6250 is broken. It's working fine if > > CONFIG_VMAP_STACK is disabled. > > > > I would be glad if it would be fixed. > > Ah, nice catch, thanks

Re: em28xx i2c writing error

Hi Frank, On Sun, Apr 16, 2017 at 7:59 PM, Frank Schäfer wrote: > > Am 15.04.2017 um 20:28 schrieb Anders Eriksson: >> Hi Mauro, >> >> I've two devices using this driver, and whenever I have them both in >> use I eventually (between 10K and 100K secs uptime) i2c

Ops in usb stack

I get oopses like this rather often on my rpi2. As can be seen it has quite a bit of USB devices attached and the odd thing is that if I disconnect either of the tv-capture devices the oopses are gone. Any ideas what triggers it? I'd be ahppy to try any patches. The call stack differs between

Re: Regression - Linux 4.9: ums_eneub6250 broken: transfer buffer not dma capable - Trace

On Mon, Apr 17, 2017 at 11:28:44AM +0200, Andreas Hartmann wrote: > Hello! > > Since Linux 4.9, ums_eneub6250 is broken. It's working fine if > CONFIG_VMAP_STACK is disabled. > > I would be glad if it would be fixed. Ah, nice catch, thanks for finding this. Does the patch below fix this for

Re: [PATCH v4] smsc95xx: Add comments to the registers definition

From: Martin Wetterwald Date: Thu, 13 Apr 2017 10:08:44 +0200 > This chip is used by a lot of embedded devices and also by the Raspberry > Pi 1, 2 & 3 which were created to promote the study of computer > sciences. Students wanting to learn kernel / network device driver >

Re: Regression - Linux 4.9: ums_eneub6250 broken: transfer buffer not dma capable - Trace

On 04/17/2017 at 09:10 PM, Alan Stern wrote: > On Mon, 17 Apr 2017, Greg KH wrote: > >> On Mon, Apr 17, 2017 at 11:28:44AM +0200, Andreas Hartmann wrote: >>> Hello! >>> >>> Since Linux 4.9, ums_eneub6250 is broken. It's working fine if >>> CONFIG_VMAP_STACK is disabled. >>> >>> I would be glad if

Re: [PATCH] usb: Make sure usb/phy/of gets built-in

On 04/13/17 05:33, Alexey Brodkin wrote: > DWC3 driver uses of_usb_get_phy_mode() which is > implemented in drivers/usb/phy/of.c and in bare minimal > configuration it might not be pulled in kernel binary. > > In case of ARC or ARM this could be easily reproduced with > "allnodefconfig"

[PATCH v2] usb: dwc3: add disable u2mac linestate check quirk

This patch adds a quirk to disable USB 2.0 MAC linestate check during HS transmit. Refer the dwc3 databook, we can use it for some special platforms if the linestate not reflect the expected line state(J) during transmission. When use this quirk, the controller implements a fixed 40-bit

[PATCH] Partially revert "usb: Kconfig: using select for USB_COMMON dependency"

This reverts commit cb9c1cfc86926d0e86d19c8e34f6c23458cd3478 for USB_LED_TRIG. This config symbol has bool type and enables extra code in usb_common itself, not a separate driver. Enabling it should not force usb_common to be built-in! Fixes: cb9c1cfc8692 ("usb: Kconfig: using select for

Regression: asix: BISECTED suspend crash - Dell XPS13-9360

Hi, Freddy, We have a bug report that system suspend crashes if the asix USB/ETHERNET adapter is connected. https://bugzilla.kernel.org/show_bug.cgi?id=195431 And the bisect result shows that  d9fe64e511144c1ee7d7555b4111f09dde9692ef is the first bad commit. commit

Re: usb: dwc2: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 146s

Hi Stefan, Am Montag, 17. April 2017, 13:05:40 CEST schrieb Stefan Wahren: > > Stefan Wahren hat am 31. Oktober 2016 um 21:34 > > geschrieben: > > > > > > I inspired by this issue [1] i build up a slightly modified setup with a > > Raspberry Pi B (mainline kernel

Re: usb: dwc2: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 146s

Hi, On Mon, Apr 17, 2017 at 4:05 AM, Stefan Wahren wrote: > Hi, > >> Stefan Wahren hat am 31. Oktober 2016 um 21:34 >> geschrieben: >> >> >> I inspired by this issue [1] i build up a slightly modified setup with a >> Raspberry Pi B (mainline