Re: [PATCH v3] usb: xhci: Issue stop EP command only when the EP state is running

On 6/22/2017 4:34 PM, Mathias Nyman wrote: > On 22.06.2017 13:44, Shyam Sundar S K wrote: >> >> On 6/19/2017 9:42 AM, Shyam Sundar S K wrote: >>> on AMD platforms with SNPS 3.1 USB controller if stop endpoint command is >>> issued the controller does not respond, when the EP is not in running

Re: [PATCH 0/3] USB Mux support for Chipidea

On 2017-07-12 03:02, Stephen Boyd wrote: > This patchset adds support for the TC7USB40MU usb mux found on > db410c 96boards platforms via the new multiplexer framework and > hooks that into the chipidea driver. This allows us to properly > control host or device mode on this board via the sysfs

[PATCH] usb: dwc3: Fix the USB 3.0 hub detection bug after warm boot

The dwc3 could not release resources when the module is built-in because this module does not have shutdown method. This causes the USB 3.0 hub is not able to detect after warm boot. Original patch by Brian Kim, updated and submitted upstream by gustavo panizzo. Also see

[PATCH 1/3] usb: misc: Add a driver for TC7USB40MU

On the db410c 96boards platform we have a TC7USB40MU[1] on the board to mux the D+/D- lines from the SoC between a micro usb "device" port and a USB hub for "host" roles. Upon a role switch, we need to change this mux to forward the D+/D- lines to either the port or the hub. Introduce a driver for

[PATCH 0/3] USB Mux support for Chipidea

This patchset adds support for the TC7USB40MU usb mux found on db410c 96boards platforms via the new multiplexer framework and hooks that into the chipidea driver. This allows us to properly control host or device mode on this board via the sysfs knob. So far I've only tested this on db410c, and

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

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 fully supports OTG with the MSM wrapper we can collapse all these nodes into one USB device node, reflecting the true nature of the

[PATCH 2/3] usb: chipidea: Hook into mux framework to toggle usb switch

On the db410c 96boards platform we have a TC7USB40MU on the board to mux the D+/D- lines coming from the controller between a micro usb "device" port and a USB hub for "host" roles[1]. During a role switch, we need to toggle this mux to forward the D+/D- lines to either the port or the hub. Add

Re: [linux-next][PATCH] usb: dwc3: core: Call dwc3_core_get_phy() before initializing phys

On 6/29/2017 12:25 AM, Vignesh R wrote: > commit f54edb539c116 ("usb: dwc3: core: initialize ULPI before trying to > get the PHY") moved call to dwc3_core_get_phy() from dwc3_probe() to > dwc3_core_init() after dwc3_core_soft_reset(). But > dwc3_core_soft_reset() calls phy_init(), therefore

Re: [PATCH V3] Set NTB format again after altsetting switch for Huawei devices

Oliver Neukum writes: > Am Dienstag, den 11.07.2017, 17:21 +0200 schrieb Enrico Mioso: >> Some firmwares in Huawei E3372H devices have been observed to switch back >> to NTB 32-bit format after altsetting switch. >> This patch implements a driver flag to check for the device

Re: [PATCH V3] Set NTB format again after altsetting switch for Huawei devices

Am Dienstag, den 11.07.2017, 17:21 +0200 schrieb Enrico Mioso: > > Some firmwares in Huawei E3372H devices have been observed to switch back > to NTB 32-bit format after altsetting switch. > This patch implements a driver flag to check for the device settings and > set NTB format to 16-bit again

Re: Bug in DWC2 UDC driver on Raspberry PI [was: g_mass_storage emulation of flash drive - difficulties with passing vendor/product ID]

On Tue, Jul 11, 2017 at 7:29 PM, Alan Stern wrote: > On Tue, 11 Jul 2017, Alan Robertson wrote: > >> Hi Alan >> >> Yes, have read about that now and certainly external build would >> definitely be quicker. >> >> However - GREAT NEWS!!! The update to 4.9.36+ seems to

Re: Bug in DWC2 UDC driver on Raspberry PI [was: g_mass_storage emulation of flash drive - difficulties with passing vendor/product ID]

On Tue, 11 Jul 2017, Alan Robertson wrote: > Hi Alan > > Yes, have read about that now and certainly external build would > definitely be quicker. > > However - GREAT NEWS!!! The update to 4.9.36+ seems to have done the trick :) > > See new dmesg... > [6.131569] 2098.usb supply vusb_d

Flashing LEDs (~1min interval) on Logitech Performance MX (USB Wireless) Mouse

Hi, I've upgraded my Distro Ubuntu from 14.04 (Kernel 3.13.0) to 16.04 (Kernel 4.4.0). Since the upgrade the battery indicator LEDs on my Logitech Performance MX Mouse light up about every 60 seconds. Depending on the charging level 1, 2 or 3 LEDs light up green. I've used the usbmon module to

Re: [PATCH v2 00/10] Constify attribute_group structures

From: Arvind Yadav Date: Tue, 11 Jul 2017 12:52:41 +0530 > attribute_groups are not supposed to change at runtime. So mark the > non-const structs as const. Please resubmit this when net-next is open again: http://vger.kernel.org/~davem/net-next.html Thank

Re: Bug in DWC2 UDC driver on Raspberry PI [was: g_mass_storage emulation of flash drive - difficulties with passing vendor/product ID]

On Tue, Jul 11, 2017 at 2:42 PM, Alan Stern wrote: > On Mon, 10 Jul 2017, Alan Robertson wrote: > >> OK have now updated to kernel 4.9.36+, unfortunately g_mass_storage >> isn't working at all in that! apt-get upgrade gave me 4.9.35+ then >> rpi-update got me to

[PATCH V3] Set NTB format again after altsetting switch for Huawei devices

Some firmwares in Huawei E3372H devices have been observed to switch back to NTB 32-bit format after altsetting switch. This patch implements a driver flag to check for the device settings and set NTB format to 16-bit again if needed. The flag has been activated for devices controlled by the

Re: [PATCH RFC V3] Set NTB format again after altsetting switch for Huawei devices

> Den 8. jul. 2017 kl. 16.39 skrev Enrico Mioso : > > Some firmwares in Huawei E3372H devices have been observed to switch back > to NTB 32-bit format after altsetting switch. > This patch implements a driver flag to check for the device settings and > set NTB format to

Re: CPU lock-ups with 4.12.0+ kernels related to usb_storage

On Tue, 11 Jul 2017, Arthur Marsh wrote: > I've had several lock-ups on recent 4.12.0+ kernels that I've built. > > The machine has an Asus M3A78 Pro motherboard and 4-core AMD CPU. > > The only usb-storage in use is an external Seagate HDD with one ntfs-3g > filesystem and another ext3

Re: Bug in DWC2 UDC driver on Raspberry PI [was: g_mass_storage emulation of flash drive - difficulties with passing vendor/product ID]

On Mon, 10 Jul 2017, Alan Robertson wrote: > OK have now updated to kernel 4.9.36+, unfortunately g_mass_storage > isn't working at all in that! apt-get upgrade gave me 4.9.35+ then > rpi-update got me to 4.9.36+. Unfortunately getting a kernel panic on > boot (even on fresh install) when

Adding new usbserial device

Hello,  I have a new device in my possession that works with usbserial generic driver.  In order for it to work I execute:  modprobe usbserial echo fff0 0100 > /sys/bus/usb-serial/drivers/generic/new_id  I'm writing to you since dmesg reads:  [ 1674.626941] usbserial_generic 4-2:1.0: Generic

Re: [PATCH] usb: dwc2: gadget: On disconnect reset device address to zero

Hi Felipe, On 7/11/2017 11:34 AM, Felipe Balbi wrote: > > Hi, > > Minas Harutyunyan writes: >>> Minas Harutyunyan writes: USB CV driver stack doesn't perform USB RESET after device disconnect/ connect, so need to reset to

[PATCH] usb: dwc2: gadget: On USB RESET reset device address to zero

Reseted DEVADDR field in DCFG to zero on USB RESET. Device address in DCFG register does not reset to zero, which required to pass enumeration, after disconnect and reconnect. Signed-off-by: Minas Harutyunyan --- drivers/usb/dwc2/gadget.c | 3 +++ 1 file changed, 3

Re: CPU lock-ups with 4.12.0+ kernels related to usb_storage

On Tue, Jul 11, 2017 at 03:30:58PM +0930, Arthur Marsh wrote: > I've had several lock-ups on recent 4.12.0+ kernels that I've built. Did older kernels work? Doing 'git bisect' would be great to track down the problem. thanks, greg k-h -- To unsubscribe from this list: send the line

Re: JMS567 USB3.0 scsi scan error

Am Montag, den 10.07.2017, 16:26 -0400 schrieb Alan Stern: > On Mon, 10 Jul 2017, Oliver Neukum wrote: > > > > > The old storage driver unconditionally limits inquiries to 36 bytes. > > > > UAS does not > > > > have that limit. That seems to be a bit optimistic. Could you test the > > > >

Re: [PATCH] usb: isp1760: compress return logic into one line

Am Montag, den 10.07.2017, 14:58 -0500 schrieb Gustavo A. R. Silva : > Hi Oliver, > > Quoting Oliver Neukum : > > > > > Am Sonntag, den 09.07.2017, 21:00 -0500 schrieb Gustavo A. R. Silva : > > > > > > Simplify return logic to avoid unnecessary variable assignment. > > > >

Re: [PATCH] usb: dwc2: gadget: On disconnect reset device address to zero

Hi, Minas Harutyunyan writes: >> Minas Harutyunyan writes: >>> USB CV driver stack doesn't perform USB RESET after device disconnect/ >>> connect, so need to reset to zero DEVADDR field in DCFG to pass >>> enumeration again. >>>

Re: [PATCH] usb: dwc2: gadget: On disconnect reset device address to zero

Hi, Minas Harutyunyan writes: >>> Minas Harutyunyan writes: USB CV driver stack doesn't perform USB RESET after device disconnect/ connect, so need to reset to zero DEVADDR field in DCFG to pass enumeration again.

[PATCH v2 00/10] Constify attribute_group structures

attribute_groups are not supposed to change at runtime. So mark the non-const structs as const. Arvind Yadav (10): [PATCH v2 01/10] net: cdc_ncm: constify attribute_group structures. [PATCH v2 02/10] net: can: at91_can: constify attribute_group structures. [PATCH v2 03/10] net: can:

[PATCH v2 01/10] net: cdc_ncm: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 13275 928 1 14204377c

Re: CPU lock-ups with 4.12.0+ kernels related to usb_storage

Matthew Dharm wrote on 11/07/17 15:54: What else is plugged in? The top line of the log snippet you sent shows an error from a USB video device... I wonder if the error occurred in a different part of the stack, and it just finally bombs-out in usb-storage Matt On Mon, Jul 10, 2017 at

Re: [PATCH 1/3] mfd: Add support for FTDI FT232H devices

On Mon, 10 Jul 2017 14:34:27 +0200 Johan Hovold jo...@kernel.org wrote: >On Fri, Jul 07, 2017 at 11:53:29AM +0200, Anatolij Gustschin wrote: >> On Fri, 07 Jul 2017 09:48:48 +0200 >> Bjørn Mork bj...@mork.no wrote: >> >> >[adding Johan on the CC list] >> > >> >Anatolij Gustschin

Re: CPU lock-ups with 4.12.0+ kernels related to usb_storage

What else is plugged in? The top line of the log snippet you sent shows an error from a USB video device... I wonder if the error occurred in a different part of the stack, and it just finally bombs-out in usb-storage Matt On Mon, Jul 10, 2017 at 11:00 PM, Arthur Marsh

CPU lock-ups with 4.12.0+ kernels related to usb_storage

I've had several lock-ups on recent 4.12.0+ kernels that I've built. The machine has an Asus M3A78 Pro motherboard and 4-core AMD CPU. The only usb-storage in use is an external Seagate HDD with one ntfs-3g filesystem and another ext3 filesystem mounted. A recent kernel log showed: Jul 11