[PATCH] dt-bindings: usb: atmel: fix a couple of copy-paste style typos

Signed-off-by: Peter Rosin --- Documentation/devicetree/bindings/usb/atmel-usb.txt | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/devicetree/bindings/usb/atmel-usb.txt b/Documentation/devicetree/bindings/usb/atmel-usb.txt index

Re: usb_ep_{dis,en}able() calling context (was: Re: [PATCH 2/3] usb: dwc3: gadget: wait for End Transfer to complete)

Hi, On 18 October 2016 at 16:21, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: >> Sure. The problem I met was, when we change the USB function with >> configfs frequently, sometimes it will hang the system to crash. The >> reason is,

Re: [PATCH] dt-bindings: usb: atmel: fix a couple of copy-paste style typos

On Tue, Oct 18, 2016 at 01:05:18PM +0200, Peter Rosin wrote: > Signed-off-by: Peter Rosin > --- > Documentation/devicetree/bindings/usb/atmel-usb.txt | 10 +- > 1 file changed, 5 insertions(+), 5 deletions(-) Acked-by: Rob Herring -- To unsubscribe

[PATCH v18 2/4] usb: gadget: Support for the usb charger framework

For supporting the usb charger, it adds the usb_charger_init() and usb_charger_exit() functions for usb charger initialization and exit. It will report to the usb charger when the gadget state is changed, then the usb charger can do the power things. Signed-off-by: Baolin Wang

[PATCH v18 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

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 v18 4/4] 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 v18 3/4] usb: gadget: Integrate with the usb gadget supporting for usb charger

When the usb gadget supporting for usb charger is ready, the usb charger can implement the usb_charger_plug_by_gadget() function, usb_charger_exit() function and dev_to_uchger() function by getting 'struct usb_charger' from 'struct gadget'. Signed-off-by: Baolin Wang

[PATCH v18 1/4] usb: gadget: Introduce the usb charger framework

This patch introduces the usb charger driver based on usb gadget that makes an enhancement to a power driver. It works well in practice but that requires a system with suitable hardware. The basic conception of the usb charger is that, when one usb charger is added or removed by reporting from

[PATCH v7, 4/8] usb: Add MediaTek USB3 DRD driver

This patch adds support for the MediaTek USB3 controller integrated into MT8173. It currently supports High-Speed Peripheral Only mode. Super-Speed Peripheral, Dual-Role Device and Host Only (xHCI) modes will be added in the next patchs. Signed-off-by: Chunfeng Yun

[PATCH v7, 3/8] usb: xhci-mtk: make IPPC register optional

Make IPPC register optional to support host side of dual-role mode, due to it is moved into common glue layer for simplification. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c | 38 +++--- drivers/usb/host/xhci-mtk.h |

[PATCH v7, 5/8] usb: mtu3: Super-Speed Peripheral mode support

add super-speed funtion for peripheral mode Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3.h| 13 ++- drivers/usb/mtu3/mtu3_core.c | 202 drivers/usb/mtu3/mtu3_gadget.c | 45 +---

[PATCH v7, 2/8] dt-bindings: mt8173-mtu3: add devicetree bindings

add a DT binding doc for MediaTek USB3 DRD driver Signed-off-by: Chunfeng Yun Acked-by: Rob Herring --- .../devicetree/bindings/usb/mt8173-mtu3.txt| 87 1 file changed, 87 insertions(+) create mode 100644

[PATCH v7, 1/8] dt-bindings: mt8173-xhci: support host side of dual-role mode

Some resources, such as IPPC register etc, shared with device driver are moved into common glue layer when xHCI driver is the host side of dual-role mode and they should be changed as optional properties if they are required ones before. For clarity, add a new part of binding to support host side

[PATCH v7, 8/8] arm64: dts: mediatek: add USB3 DRD driver

USB3 DRD driver is added for MT8173-EVB, and xHCI driver becomes its subnode Signed-off-by: Chunfeng Yun --- arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 63 ++- arch/arm64/boot/dts/mediatek/mt8173.dtsi| 29 +--- 2 files

[PATCH v7, 7/8] usb: mtu3: dual-role mode support

support dual-role mode; there are two ways to switch between host and device modes, one is by idpin, another is by debugfs which depends on user input. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/Kconfig | 15 +- drivers/usb/mtu3/Makefile | 11 +-

[PATCH v7, 6/8] usb: mtu3: host only mode support

supports host only mode and the code is ported from host/xhci-mtk.c IPPC register shared between host and device is moved into common glue layer. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/Kconfig |9 ++ drivers/usb/mtu3/Makefile| 11 +-

[PATCH v7, 0/8] Add MediaTek USB3 DRD Driver

These patches introduce the MediaTek USB3 dual-role controller driver. The driver can be configured as Dual-Role Device (DRD), Peripheral Only and Host Only (xHCI) modes. It works well with Mass Storage, RNDIS and g_zero on FS/HS and SS. And it is tested on MT8173 platform which only contains

Re: [PATCH v5 11/23] usb: chipidea: Emulate OTGSC interrupt enable path

On Mon, Oct 17, 2016 at 06:56:24PM -0700, Stephen Boyd wrote: > In the case of an extcon-usb-gpio device being used with the > chipidea driver we'll sometimes miss the BSVIS event in the OTGSC > register. Consider the case where we don't have a cable attached > and the id pin is indicating "host"

[PATCH 1/1] usb: xhci: clean up error_bitmask usage

In xhci_handle_event(), when errors are detected, driver always sets a bit in error_bitmask (one member of the xhci private driver data). That means users have to retrieve and decode the value of error_bitmask in xhci private driver data if they want to know whether those erros ever happened in

[RESEND PATCH v2 4/4] usb: doc: add document for USB3 debug port usage

Add Documentation/usb/usb3-debug-port.txt. This document includes the user guide for USB3 debug port. Cc: linux-...@vger.kernel.org Signed-off-by: Lu Baolu --- Documentation/usb/usb3-debug-port.txt | 87 +++ 1 file changed, 87

[RESEND PATCH v2 0/4] usb: early: add support for early printk through USB3 debug port

xHCI debug capability (DbC) is an optional but standalone functionality provided by an xHCI host controller. With DbC hardware initialized, the system will present a debug device through the USB3 debug port (normally the first USB3 port). The debug device is fully compliant with the USB framework

[RESEND PATCH v2 3/4] usb: serial: usb_debug: add support for dbc debug device

This patch add dbc debug device support in usb_debug driver. Signed-off-by: Lu Baolu Acked-by: Johan Hovold --- drivers/usb/serial/usb_debug.c | 28 +--- 1 file changed, 25 insertions(+), 3 deletions(-) diff --git

[RESEND PATCH v2 2/4] x86: add support for earlyprintk via USB3 debug port

Add support for early printk by writing debug messages to the USB3 debug port. Users can use this type of early printk by specifying kernel parameter of "earlyprintk=xdbc". This gives users a chance of providing debug output. The hardware for USB3 debug port requires DMA memory blocks. This

[RESEND PATCH v2 1/4] usb: dbc: early driver for xhci debug capability

xHCI debug capability (DbC) is an optional but standalone functionality provided by an xHCI host controller. Software learns this capability by walking through the extended capability list of the host. xHCI specification describes DbC in section 7.6. This patch introduces the code to probe and

Re: [RFC][PATCH 2/2] usb: dwc2: Add a quirk to allow speed negotiation for Hisilicon Hi6220

On 10/16/2016 7:42 PM, Chen Yu wrote: > > > On 2016/10/15 3:37, John Youn wrote: >> On 10/13/2016 4:36 PM, John Stultz wrote: >>> From: Chen Yu >>> >>> The Hi6220's usb controller is limited in that it does not >>> automatically autonegotiate the usb speed. Thus it requires

Re: [PATCH] xhci: Fix dereference from empty xhci->cmd_list

Mathias Nyman writes: >> OGAWA Hirofumi writes: >>> If race with timeout or stop event on empty cmd_list was happened, >>> handle_cmd_completion() deferences wrong pointer from xhci->cmd_list. >>> >>> So this makes sure we don't dereference

[PATCH v2 49/58] zr364xx: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

Re: [PATCH net-next] r8152: add new products of Lenovo

From: Hayes Wang Date: Tue, 18 Oct 2016 11:41:48 +0800 > Add the following four products of Lenovo and sort the order of the list. > > VID PID > 0x17ef 0x3062 > 0x17ef 0x3069 > 0x17ef 0x720c > 0x17ef

Re: [PATCH v5 03/23] usb: ulpi: Support device discovery via DT

On Mon, Oct 17, 2016 at 06:56:16PM -0700, Stephen Boyd wrote: > The qcom HSIC ULPI phy doesn't have any bits set in the vendor or > product ID registers. This makes it impossible to make a ULPI > driver match against the ID registers. Add support to discover > the ULPI phys via DT help alleviate

Re: [PATCH v5 23/23] phy: Add support for Qualcomm's USB HS phy

On Mon, Oct 17, 2016 at 06:56:36PM -0700, Stephen Boyd wrote: > The high-speed phy on qcom SoCs is controlled via the ULPI > viewport. > > Cc: Kishon Vijay Abraham I > Cc: > Cc: Rob Herring > Signed-off-by: Stephen Boyd

Re: [PATCH v5 23/23] phy: Add support for Qualcomm's USB HS phy

On Mon, Oct 17, 2016 at 06:56:36PM -0700, Stephen Boyd wrote: > The high-speed phy on qcom SoCs is controlled via the ULPI > viewport. > > Cc: Kishon Vijay Abraham I > Cc: > Cc: Rob Herring > Signed-off-by: Stephen Boyd

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote: > Oct 18 14:05:07 linux-dtbq.site kernel: usb 1-9: Manufacturer: Conexant > Oct 18 14:05:07 linux-dtbq.site kernel: usb 1-9: SerialNumber: 12345678 With that unique serial number it must be that very device. :-) > It definitely does

Re: [PATCH] xhci: Fix dereference from empty xhci->cmd_list

Hi On 18.10.2016 16:07, Felipe Balbi wrote: Hi, OGAWA Hirofumi writes: If race with timeout or stop event on empty cmd_list was happened, handle_cmd_completion() deferences wrong pointer from xhci->cmd_list. So this makes sure we don't dereference wrong pointer

Re: [alsa-devel] Jack sensing in snd_usb_audio ?

On Tue, 18 Oct 2016 15:33:42 +0200, Felipe Ferreri Tonello wrote: > > Hi Takashi > > On 18/10/16 13:07, Takashi Iwai wrote: > > On Wed, 12 Oct 2016 18:15:04 +0200, > > Bastien Nocera wrote: > >> > >> On Wed, 2016-10-12 at 18:06 +0200, Clemens Ladisch wrote: > >>> Bastien Nocera wrote: > On

Re: [PATCH 2/4] USB: ch341: reinitialize chip on reconfiguration

On Tue, Oct 18, 2016 at 12:39:23PM -, Karl Palsson wrote: > > Johan Hovold wrote: > > On Sun, Oct 16, 2016 at 05:09:24PM +0100, Aidan Thornton wrote: > > > On Mon, Oct 10, 2016 at 8:56 PM, Grigori Goronzy > > > wrote: > > > > On 2016-10-08 23:07, Aidan

Re: [alsa-devel] Jack sensing in snd_usb_audio ?

Hi Takashi On 18/10/16 13:07, Takashi Iwai wrote: > On Wed, 12 Oct 2016 18:15:04 +0200, > Bastien Nocera wrote: >> >> On Wed, 2016-10-12 at 18:06 +0200, Clemens Ladisch wrote: >>> Bastien Nocera wrote: On Wed, 2016-10-12 at 14:43 +0200, Clemens Ladisch wrote: > Bastien Nocera wrote:

Re: [PATCH] xhci: Fix dereference from empty xhci->cmd_list

Hi, OGAWA Hirofumi writes: > If race with timeout or stop event on empty cmd_list was happened, > handle_cmd_completion() deferences wrong pointer from xhci->cmd_list. > > So this makes sure we don't dereference wrong pointer from empty > xhci->cmd_list. > >

[PATCH] xhci: Fix dereference from empty xhci->cmd_list

If race with timeout or stop event on empty cmd_list was happened, handle_cmd_completion() deferences wrong pointer from xhci->cmd_list. So this makes sure we don't dereference wrong pointer from empty xhci->cmd_list. Signed-off-by: OGAWA Hirofumi ---

Re: [PATCH 2/4] USB: ch341: reinitialize chip on reconfiguration

Johan Hovold wrote: > On Sun, Oct 16, 2016 at 05:09:24PM +0100, Aidan Thornton wrote: > > On Mon, Oct 10, 2016 at 8:56 PM, Grigori Goronzy wrote: > > > On 2016-10-08 23:07, Aidan Thornton wrote: > > >> > > >> On Fri, Oct 7, 2016 at 12:30 PM, Johan Hovold

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

On Mon, 2016-10-17 at 17:20 +0200, Wim Osterholt wrote: > On Mon, Oct 17, 2016 at 04:10:45PM +0200, Oliver Neukum wrote: > > Hi, > > > > I got one of those devices. However, I don't get a crash. > > Could you please give me instructions on how you trigger it? > > That's not too hard, just

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi, On Mon, 2016-10-17 at 15:21 +0530, Vivek Gautam wrote: > > On 10/17/2016 01:38 PM, Felipe Balbi wrote: > > Hi, > > > > Michael Niewöhner writes: > > > Hi Felipe, > > > On Fri, 2016-10-07 at 22:26 +0200, Michael Niewöhner wrote: > > > > Hi Felipe, > > > > > > > > On

Re: [alsa-devel] Jack sensing in snd_usb_audio ?

On Wed, 12 Oct 2016 18:15:04 +0200, Bastien Nocera wrote: > > On Wed, 2016-10-12 at 18:06 +0200, Clemens Ladisch wrote: > > Bastien Nocera wrote: > > > On Wed, 2016-10-12 at 14:43 +0200, Clemens Ladisch wrote: > > > > Bastien Nocera wrote: > > > > > " > > > > > A change of state in the audio

Re: [PATCH 2/4] USB: ch341: reinitialize chip on reconfiguration

On Sun, Oct 16, 2016 at 05:09:24PM +0100, Aidan Thornton wrote: > On Mon, Oct 10, 2016 at 8:56 PM, Grigori Goronzy wrote: > > On 2016-10-08 23:07, Aidan Thornton wrote: > >> > >> On Fri, Oct 7, 2016 at 12:30 PM, Johan Hovold wrote: > >>> > >>> Why is this

Re: [PATCH] dt-bindings: usb: atmel: fix a couple of copy-paste style typos

Le 18/10/2016 à 13:05, Peter Rosin a écrit : > Signed-off-by: Peter Rosin Acked-by: Nicolas Ferre We may take it in a future at91-x.y-dt branch which will go through arm-soc. Thanks > --- > Documentation/devicetree/bindings/usb/atmel-usb.txt | 10

Re: usb: dwc2: Revert incorrect FIFO changes

Hi, John Youn writes: > This series reverts patches that incorrectly removed some FIFO > programming. > > Hi Felipe, > > This fixes a regression on 4.9-rc1, could you queue them in your fixes > tree? added to testing/fixes. I'll be sending a pull request tomorrow if I

Re: [PATCH v5 00/23] Support qcom's HSIC USB and rewrite USB2 HS support

On Mon, Oct 17, 2016 at 06:56:13PM -0700, Stephen Boyd wrote: > The state of USB ChipIdea support on Qualcomm's platforms is not great. > The DT description of these devices requires up to three different nodes > for what amounts to be the same hardware block, when there should really > only be

Re: usb_ep_{dis,en}able() calling context (was: Re: [PATCH 2/3] usb: dwc3: gadget: wait for End Transfer to complete)

Hi, Baolin Wang writes: >> >> 8< >> >> From f3fa94f3171709f787a30e3c5ce69a668960b66e Mon Sep 17 00:00:00 2001 >> >> From: Felipe Balbi >> >> Date: Thu,

Re: usb_ep_{dis,en}able() calling context (was: Re: [PATCH 2/3] usb: dwc3: gadget: wait for End Transfer to complete)

On Tue, Oct 18, 2016 at 10:19:38AM +0300, Felipe Balbi wrote: > > Hi, > > Alan Stern writes: > >> Baolin Wang writes: > >> >> Felipe Balbi writes: > >> >>> Instead of just delaying for 100us, we should > >> >>>

Re: usb_ep_{dis,en}able() calling context (was: Re: [PATCH 2/3] usb: dwc3: gadget: wait for End Transfer to complete)

On 18 October 2016 at 16:21, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: >>> Alan Stern writes: > Baolin Wang writes: > >> Felipe Balbi

Re: usb_ep_{dis,en}able() calling context (was: Re: [PATCH 2/3] usb: dwc3: gadget: wait for End Transfer to complete)

Hi, Baolin Wang writes: >> Alan Stern writes: Baolin Wang writes: >> Felipe Balbi writes: >>> Instead of just delaying for 100us, we should >>> actually wait for End

Re: usb_ep_{dis,en}able() calling context (was: Re: [PATCH 2/3] usb: dwc3: gadget: wait for End Transfer to complete)

Hi, On 18 October 2016 at 15:19, Felipe Balbi wrote: > > Hi, > > Alan Stern writes: >>> Baolin Wang writes: >>> >> Felipe Balbi writes: >>> >>> Instead of just delaying for 100us, we

Re: usb_ep_{dis,en}able() calling context (was: Re: [PATCH 2/3] usb: dwc3: gadget: wait for End Transfer to complete)

Hi, Alan Stern writes: >> Baolin Wang writes: >> >> Felipe Balbi writes: >> >>> Instead of just delaying for 100us, we should >> >>> actually wait for End Transfer Command Complete >> >>> interrupt before moving

RE: USB GADGET: have a question about usb2eth

Hi, Lipengcheng writes: >> -Original Message- >> From: Felipe Balbi [mailto:ba...@kernel.org] >> Sent: Monday, October 17, 2016 5:29 PM >> To: Lipengcheng; Peter Chen >> Cc: gre...@linuxfoundation.org; linux-usb@vger.kernel.org; >> linux-ker...@vger.kernel.org >>