Re: [PATCH 1/1] usb: xhci: Handle USB transaction error on address command

Hi, On 07/26/2017 01:11 PM, Xing, Zhengjun wrote: > > > On 7/25/2017 1:09 PM, Lu Baolu wrote: >> Xhci driver handles USB transaction errors on transfer events, >> but transaction errors are possible on address device command >> completion events as well. >> >> The xHCI specification (section

Re: USB 3.0 is broken on Odroid Xu4 on latest kernel

Hi Krzysztof / Felipe, On 20 July 2017 at 01:50, Krzysztof Kozlowski wrote: > On Wed, Jul 19, 2017 at 09:13:29PM +0300, Felipe Balbi wrote: >> >> Hi, >> >> Anand Moon writes: >> > Hi Krzysztof, >> > >> > Today I tried to compile the latest kernel for

Re: [PATCH v3 2/3] usb: phy: Add USB charger support

Hi Manu, On 25 July 2017 at 19:19, Manu Gautam wrote: > Hi, > > > On 7/25/2017 1:30 PM, Baolin Wang wrote: >> This patch introduces the usb charger support based on usb phy that >> makes an enhancement to a power driver. The basic conception of the >> usb charger is that,

Re: [PATCH v3 3/3] power: wm831x_power: Support USB charger current limit management

Hi, On 25 July 2017 at 17:59, Sebastian Reichel wrote: > Hi, > > On Tue, Jul 25, 2017 at 04:00:01PM +0800, Baolin Wang wrote: >> Integrate with the newly added USB charger interface to limit the current >> we draw from the USB input based on the input device

[PATCH] uas: Add US_FL_IGNORE_RESIDUE for Initio Copropration INIC-3069

Similar to commit d595259fbb7a7afed241b1afb2c4fe4b47de47fa for INIC-3169 in unusual_devs.h but INIC-3069 already present in unusual_uas.h. Both in same controller IC family. Issue is that MakeMKV fails during key exchange with installed bluray drive with following error: 002004: Error 'Scsi

[PATCH] USB: hcd: Mark secondary HCD as dead if the primary one died

From: Rafael J. Wysocki Make usb_hc_died() clear the HCD_FLAG_RH_RUNNING flag for the shared HCD and set HCD_FLAG_DEAD for it, in analogy with what is done for the primary one. Among other thigs, this prevents check_root_hub_suspended() from returning -EBUSY for dead

Re: [PATCH] PM / USB: hcd_pci: Skip secondary root hub check for HCD_DEAD()

On Tuesday, July 25, 2017 05:06:40 PM Alan Stern wrote: > On Tue, 25 Jul 2017, Rafael J. Wysocki wrote: > > > On Tuesday, July 25, 2017 05:59:04 PM Rafael J. Wysocki wrote: > > > On Tuesday, July 25, 2017 10:05:03 AM Alan Stern wrote: > > > > On Tue, 25 Jul 2017, Rafael J. Wysocki wrote: > > > >

Re: Please help me with kernel hung

On Wed, 26 Jul 2017, Михаил Гаврилов wrote: > On 25 July 2017 at 02:12, Alan Stern wrote: > > This is enough for now. The problem is that a USB transfer is started > > but never stopped, which indicates a problem with the host controller. > > > > In this case you're

Re: [PATCH] PM / USB: hcd_pci: Skip secondary root hub check for HCD_DEAD()

On Tue, 25 Jul 2017, Rafael J. Wysocki wrote: > On Tuesday, July 25, 2017 05:59:04 PM Rafael J. Wysocki wrote: > > On Tuesday, July 25, 2017 10:05:03 AM Alan Stern wrote: > > > On Tue, 25 Jul 2017, Rafael J. Wysocki wrote: > > > > > > > From: Rafael J. Wysocki > > >

Re: [PATCH] PM / USB: hcd_pci: Skip secondary root hub check for HCD_DEAD()

On Tuesday, July 25, 2017 05:59:04 PM Rafael J. Wysocki wrote: > On Tuesday, July 25, 2017 10:05:03 AM Alan Stern wrote: > > On Tue, 25 Jul 2017, Rafael J. Wysocki wrote: > > > > > From: Rafael J. Wysocki > > > > > > If HCD_DEAD(hcd) is "true" in

Re: Please help me with kernel hung

On 25 July 2017 at 02:12, Alan Stern wrote: > This is enough for now. The problem is that a USB transfer is started > but never stopped, which indicates a problem with the host controller. > > In this case you're using an xHCI host controller. Unfortunately the > xHCI

Re: No Ethernet on Raspberry Pi 3 in v4.13-rc1

> Robin Murphy hat am 25. Juli 2017 um 15:21 geschrieben: > > > Hi Stefan, > > On 25/07/17 06:19, Stefan Wahren wrote: > >>> With arm64 4.13-rc1 I get no eth0 device on Pi3 (openSUSE Tumbleweed). > >>> The v4.13-rc1 DT works okay with a 4.12 kernel. > >>> > >>> Possibly

Re: [RFCv2 usb-next 2/3] usb: host: add a generic platform USB roothub driver

On Tue, Jul 25, 2017 at 8:40 AM, Chunfeng Yun wrote: > On Thu, 2017-07-13 at 12:59 +0200, Martin Blumenstingl wrote: >> Many SoC platforms have separate devices for the USB PHY which are >> registered through the generic PHY framework. These PHYs have to be >> enabled

Re: No Ethernet on Raspberry Pi 3 in v4.13-rc1

> Robin Murphy hat am 25. Juli 2017 um 15:21 geschrieben: > > From the subsequent fallout (which on closer inspection looks more to do > with calling into uninitialised SWIOTLB state than the arm64 DMA code > actually doing anything wrong), I'd guess dev->dma_pfn_offset is

Re: [PATCH] PM / USB: hcd_pci: Skip secondary root hub check for HCD_DEAD()

On Tuesday, July 25, 2017 10:05:03 AM Alan Stern wrote: > On Tue, 25 Jul 2017, Rafael J. Wysocki wrote: > > > From: Rafael J. Wysocki > > > > If HCD_DEAD(hcd) is "true" in check_root_hub_suspended(), it is > > rather pointless to check the secondary root hub, so

Re: [PATCH] USB: musb: fix external abort on suspend

On Tue, 25 Jul 2017, Johan Hovold wrote: > On Mon, Jul 24, 2017 at 01:13:22PM -0400, Alan Stern wrote: > > On Mon, 24 Jul 2017, Johan Hovold wrote: > > > > > On Mon, Jul 24, 2017 at 10:38:41AM -0400, Alan Stern wrote: > > > > On Mon, 24 Jul 2017, Johan Hovold wrote: > > > > > > > > > Make sure

pixart optical mouse dont work

dear kernel hackers, with the new kernel 4.13 my optical mouse from pixart dont work but i can show it with lsusb bus 007 device 003: id 093a:2510 pixart imaging,inc optical mouse i changed nothing in my kernel .conf with kernel 4.12, 4.11...i had no problems i guess its something with the

[PATCH 1/2] usb: core: unlink urbs from the tail of the endpoint's urb_list

While unlink an urb, if the urb has been programmed in the controller, the controller driver might do some hw related actions to tear down the urb. Currently usb_hcd_flush_endpoint() passes each urb from the head of the endpoint's urb_list to the controller driver, which could make the controller

[PATCH 2/2] usb: musb: fix tx fifo flush handling again

commit 68fe05e2a451 ("usb: musb: fix tx fifo flush handling") drops the 1ms delay trying to solve the long disconnect time issue when application queued many tx urbs. However, the 1ms delay is needed for some use cases, for example, without the delay, reconnecting AR9271 WIFI dongle no longer

[PATCH 0/2] musb-fixes for v4.13-rc3

Hi Greg, Here is a musb fix for v4.13-rc3, for the re-enumeration issue exposed by AM9271 WIFI dongle. Please let me know if any change is needed. Regards, -Bin. --- Bin Liu (2): usb: core: unlink urbs from the tail of the endpoint's urb_list usb: musb: fix tx fifo flush handling again

ERROR Transfer event TRB DMA ptr not part of current TD ep_index 0 comp_code 3

Hello, I am trying to help somebody fix this longtime bug in xhci_hcd driver. (or more likely bug in ASMedia controller that we co I will try provide as much information as I can. My setup: I am using USB TV tuner card connected to ASMedia USB 3.1 port on mainboard. 00:00.0 USB controller:

Re: [PATCH] PM / USB: hcd_pci: Skip secondary root hub check for HCD_DEAD()

On Tue, 25 Jul 2017, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > If HCD_DEAD(hcd) is "true" in check_root_hub_suspended(), it is > rather pointless to check the secondary root hub, so return early > then. > > This actually fixes occasional suspend

Re: No Ethernet on Raspberry Pi 3 in v4.13-rc1

Hi Stefan, On 25/07/17 06:19, Stefan Wahren wrote: >>> With arm64 4.13-rc1 I get no eth0 device on Pi3 (openSUSE Tumbleweed). >>> The v4.13-rc1 DT works okay with a 4.12 kernel. >>> >>> Possibly related: >>> >>> [ 15.916350] OF: /soc/usb@7e98: could not get #phy-cells for /phy >>> >>> [

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

On Tue, 25 Jul 2017 13:49:08 +0200 Johan Hovold jo...@kernel.org wrote: >On Wed, Jul 19, 2017 at 01:58:30PM +0200, Anatolij Gustschin wrote: >> On Mon, 10 Jul 2017 14:52:10 +0200 >> Johan Hovold jo...@kernel.org wrote: >> >> >On Thu, Jul 06, 2017 at 10:49:16PM +0200, Anatolij Gustschin wrote:

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

On Tue, 25 Jul 2017 13:52:35 +0200 Johan Hovold jo...@kernel.org wrote: >On Wed, Jul 19, 2017 at 02:59:00PM +0200, Anatolij Gustschin wrote: >> On Wed, 19 Jul 2017 10:59:34 +0200 >> Johan Hovold jo...@kernel.org wrote: > >> >> And as David Laight already pointed out, your ftdi-fifo-fpp-mgr

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

On Wed, Jul 19, 2017 at 02:59:00PM +0200, Anatolij Gustschin wrote: > On Wed, 19 Jul 2017 10:59:34 +0200 > Johan Hovold jo...@kernel.org wrote: > >> And as David Laight already pointed out, your ftdi-fifo-fpp-mgr driver > >> seems too application specific for a generic chip like this. > > > >Of

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

On Wed, Jul 19, 2017 at 01:58:30PM +0200, Anatolij Gustschin wrote: > On Mon, 10 Jul 2017 14:52:10 +0200 > Johan Hovold jo...@kernel.org wrote: > > >On Thu, Jul 06, 2017 at 10:49:16PM +0200, Anatolij Gustschin wrote: > >> Add USB part with common functions for USB-GPIO/I2C/SPI master > >>

Re: [PATCH] USB: serial: ftdi_sio: only bind FT232H if UART mode is enabled

On Wed, Jul 19, 2017 at 01:23:27PM +0200, Anatolij Gustschin wrote: > On Wed, 19 Jul 2017 11:03:11 +0200 > Johan Hovold jo...@kernel.org wrote: > > >On Thu, Jul 13, 2017 at 06:25:25PM +0200, Anatolij Gustschin wrote: > >> On FT232H the interface mode can be configured in the EEPROM, > >> and the

Re: [PATCH v3 2/3] usb: phy: Add USB charger support

Hi, On 7/25/2017 1:30 PM, Baolin Wang wrote: > This patch introduces the usb charger support based on usb phy that > makes an enhancement to a power driver. The basic conception of the > usb charger is that, when one usb charger is added or removed by > reporting from the extcon device state

Re: [PATCH v3 3/3] power: wm831x_power: Support USB charger current limit management

Hi, On Tue, Jul 25, 2017 at 04:00:01PM +0800, Baolin Wang wrote: > Integrate with the newly added USB charger interface to limit the current > we draw from the USB input based on the input device configuration > identified by the USB stack, allowing us to charge more quickly from high > current

Re: [PATCH v3 3/3] power: wm831x_power: Support USB charger current limit management

On Tue, Jul 25, 2017 at 04:00:01PM +0800, Baolin Wang wrote: > Integrate with the newly added USB charger interface to limit the current > we draw from the USB input based on the input device configuration > identified by the USB stack, allowing us to charge more quickly from high > current inputs

Re: [PATCH v3 3/3] power: wm831x_power: Support USB charger current limit management

On Tue, 25 Jul 2017, Baolin Wang wrote: > Integrate with the newly added USB charger interface to limit the current > we draw from the USB input based on the input device configuration > identified by the USB stack, allowing us to charge more quickly from high > current inputs without drawing

Re: v4.13-rc2: usb mouse stopped working?

Jiri Kosina writes: > On Mon, 24 Jul 2017, Pavel Machek wrote: > > > On thinkpad x220, USB mouse stopped working in v4.13-rc2. v4.12 was > > ok, iirc. > > > > Now, USB mouse is so common hw that I may have something wrong in my > > config...? But I did not change anything there. > >

[PATCH 2/3] usb: mtu3: clear u1/u2_enable to 0 in mtu3_gadget_reset

when the device is reset by host, the status of u1_enable and u2_enable should also be restored to default value. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_gadget.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/usb/mtu3/mtu3_gadget.c

[PATCH 3/3] usb: mtu3: fix ip sleep auto-exit issue when enable DRD mode

Ip sleep will auto exit if vbus comparison circuit of u2 phy is disabled when system tries to enter suspend mode, so get vbus-valid status from mac but not from u2 phy when enable DRD mode to fix the issue. Signed-off-by: Chunfeng Yun ---

[PATCH 1/3] usb: mtu3: handle delayed status of the control transfer

Add the delayed status handling. This is used by mass storage etc to gain some extra time to setup its internal status before it can proceed further requests, and once the gadget is ready, it will enqueue an empty packet which is used for synchronization. The issue may happen on some FGPA platform

[PATCH v3 0/3] Introduce USB charger support in USB phy

Currently the Linux kernel does not provide any standard integration of this feature that integrates the USB subsystem with the system power regulation provided by PMICs meaning that either vendors must add this in their kernels or USB gadget devices based on Linux (such as mobile phones) may not

[PATCH v3 1/3] include: uapi: usb: Introduce USB charger type and state definition

Introducing USB charger type and state definition can help to support USB charging which will be added in USB phy core. Signed-off-by: Baolin Wang --- include/uapi/linux/usb/charger.h | 31 +++ 1 file changed, 31 insertions(+) create mode

[PATCH v3 3/3] power: wm831x_power: Support USB charger current limit management

Integrate with the newly added USB charger interface to limit the current we draw from the USB input based on the input device configuration identified by the USB stack, allowing us to charge more quickly from high current inputs without drawing more current than specified from others.

[PATCH v3 2/3] usb: phy: Add USB charger support

This patch introduces the usb charger support based on usb phy that makes an enhancement to a power driver. The basic conception of the usb charger is that, when one usb charger is added or removed by reporting from the extcon device state change, the usb charger will report to power user to set

Re: [PATCH] USB: musb: fix external abort on suspend

On Mon, Jul 24, 2017 at 01:13:22PM -0400, Alan Stern wrote: > On Mon, 24 Jul 2017, Johan Hovold wrote: > > > On Mon, Jul 24, 2017 at 10:38:41AM -0400, Alan Stern wrote: > > > On Mon, 24 Jul 2017, Johan Hovold wrote: > > > > > > > Make sure that the controller is runtime resumed when system

Re: [RFCv2 usb-next 2/3] usb: host: add a generic platform USB roothub driver

On Thu, 2017-07-13 at 12:59 +0200, Martin Blumenstingl wrote: > Many SoC platforms have separate devices for the USB PHY which are > registered through the generic PHY framework. These PHYs have to be > enabled to make the USB controller actually work. They also have to be > disabled again on