[PATCH v2 1/3] USB: serial: cp210x: Fixed RTS mode setting by the CRTSCTS flag.

A bug in the CRTSCTS handling caused RTS to alternate between CRTSCTS=0 => "RTS transmits active signal" and CRTSCTS=1 => "RTS receives flow control" instead of CRTSCTS=0 => "RTS is statically active" and CRTSCTS=1 => "RTS receives flow control" This only happened after first having enabled

[PATCH v2 2/3] USB: serial: cp210x: Added comments to CRTSCTS flag code.

Replaced magic numbers used in the CRTSCTS flag code with symbolic names from the chip specification. Signed-off-by: Konstantin Shkolnyy --- Changes in v2: Improved CRTSCTS fix based on feedback. Dropped get_termios error handling. drivers/usb/serial/cp210x.c |

[PATCH v2 3/3] USB: serial: cp210x: Cleaned up CRTSCTS flag code.

The CRTSCTS flag code cleared (and inconsistently) bits unrelated to CRTSCTS functionality. It was also harder than necessary to read. Signed-off-by: Konstantin Shkolnyy --- Changes in v2: Improved CRTSCTS fix based on feedback. Dropped get_termios error handling.

Re: [PATCHv3] usb: Add driver for UCSI

On Fri, Apr 29, 2016 at 04:32:22PM +0300, Heikki Krogerus wrote: > Hi Greg, > > On Thu, Apr 28, 2016 at 12:53:24PM -0700, Greg Kroah-Hartman wrote: > > On Thu, Apr 21, 2016 at 03:43:40PM +0300, Heikki Krogerus wrote: > > > USB Type-C Connector System Software Interface (UCSI) is > > >

Re: [GIT PULL] USB-serial fixes for v4.6-rc6

On Fri, Apr 29, 2016 at 10:23:28AM +0200, Johan Hovold wrote: > Hi Greg, > > Here are some new device ids for rc6. These have been in next for a few > days now without any issues. > > Thanks, > Johan > > The following changes since commit c3b46c73264b03000d1e18b22f5caf63332547c9: > > Linux

Re: [PATCH v2] xhci: Cleanup only when releasing primary hcd.

On 04/28/2016 04:30 AM, Roger Quadros wrote: > Hi Joe, > > On 27/04/16 23:41, Joe Lawrence wrote: >> Hello Mathias, Roger, Gabriel >> >> [ ... snip ... ] >> In the meantime I was browsing recent linux-scsi archives and noticed >> Gabriel's [PATCH v2] xhci: Cleanup only when releasing primary

[PATCH] USB: leave LPM alone if possible when binding/unbinding interface drivers

When a USB driver is bound to an interface (either through probing or by claiming it) or is unbound from an interface, the USB core always disables Link Power Management during the transition and then re-enables it afterward. The reason is because the driver might want to prevent hub-initiated

[PATCH v2] USB: EHCI: make all debugging depend on CONFIG_DYNAMIC_DEBUG

The debugging facilities in ehci-dbg.c follow an uneven pattern. Some of them are protected by "#ifdef CONFIG_DYNAMIC_DEBUG" and some aren't, presumably in the hope of having some of the debugging output available in any configuration. This leads to build problems when dynamic debugging isn't

Re: [PATCH] USB: EHCI: make all debugging depend on CONFIG_DYNAMIC_DEBUG

On Thu, 28 Apr 2016, Greg KH wrote: > On Fri, Apr 15, 2016 at 12:12:26PM -0400, Alan Stern wrote: > > The debugging facilities in ehci-dbg.c follow an uneven pattern. Some > > of them are protected by "#ifdef CONFIG_DYNAMIC_DEBUG" and some > > aren't, presumably in the hope of having some of the

[FWD: Alan's latest patch]

Good morning Alan, I just finished testing your latest patch on Ubuntu 14.04.4 LTS (4.2.x kernel) and Ubuntu 16.04 LTS (4.4.x kernel) on x86/x64, and it resolves the issues I've encountered. May we please have this patch submitted for review? Thank you and the linux-usb developers for your time

RE: [EXT] Re: [PATCH] Add DCD line support to CP210x driver

> -Original Message- > From: Johan Hovold [mailto:jhov...@gmail.com] On Behalf Of Johan Hovold > Sent: Friday, April 29, 2016 05:09 > To: Valentin Yakovenkov > Cc: Konstantin Shkolnyy; linux-usb@vger.kernel.org > Subject: [EXT] Re: [PATCH] Add DCD line support to CP210x driver > > On Thu,

Re: [RFT PATCH 1/3] usb: misc: usb3503: Fix HUB mode after bootloader initialization

On Fri, Apr 29, 2016 at 01:55:14PM +0200, Krzysztof Kozlowski wrote: > On 04/29/2016 01:30 PM, Mark Brown wrote: > > Supplies are only optional if they may be physically absent. In this > > case it's possible that on device regulators may be used instead, a > > pattern more like that used for

[GIT PULL v2 4/4]: ARM: tegra: Enable the XUSB controller

The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca: Linux 4.6-rc1 (2016-03-26 16:03:24 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.7-xusb-no-defconfig for you to fetch changes up to

[GIT PULL 3/4]: usb: host: xhci-tegra: Changes for v4.7-rc1

The following changes since commit 87d66f280672800c9c2ad1ce3b7a993ce1e04769: phy: tegra: Add Tegra210 support (2016-04-29 16:44:48 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.7-xhci for you to fetch changes

[GIT PULL 4/4]: ARM: tegra: Enable the XUSB controller

The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca: Linux 4.6-rc1 (2016-03-26 16:03:24 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.7-xusb for you to fetch changes up to

Re: [PATCH 03/10] usb: musb: Fix PM runtime handling for connected cable

* Tony Lindgren [160428 11:09]: > * Sergei Shtylyov [160428 10:55]: > > >+ cable_connected = ((glue->status & MUSB_ID_GROUND) || > > >+ (glue->status & MUSB_VBUS_VALID)); > > > > cable_connected = glue->status &

[GIT PULL 1/4]: phy: tegra: Changes for v4.7-rc1

The following changes since commit 3358d2d9f47af86bdd71edb24b361f72a54ec04e: clk: tegra: Add interface to enable hardware control of SATA/XUSB PLLs (2016-04-28 12:41:44 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git

[GIT PULL 2/4]: PCI: tegra: Changes for v4.7-rc1

The following changes since commit 87d66f280672800c9c2ad1ce3b7a993ce1e04769: phy: tegra: Add Tegra210 support (2016-04-29 16:44:48 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.7-pci for you to fetch changes

[GIT PULL 0/4] ARM: tegra: Add XUSB controller support

Hi everyone, This is a fairly complicated series of pull requests because of the dependencies involved. The goal is to take all of the patches through the ARM-SoC tree but I'm sending out these individual pull requests to document this. Also, if these branches were starting to cause conflicts

Re: [PATCH] usb: gadget: f_fs: Fix kernel panic for SuperSpeed

On 28.04.2016 15:21, Felipe Balbi wrote: Hi, dmesg from PC host side (after adding your change without my patch): [17907.984647] usb 6-2: new SuperSpeed USB device number 54 using xhci_hcd [17908.012036] usb 6-2: No SuperSpeed endpoint companion for config 1 interface 1 altsetting 0 ep 2:

Re: [PATCH v4 04/13] USB: ch341: fix USB buffer allocations

On 2016-04-29 14:52, Johan Hovold wrote: @@ -168,9 +168,9 @@ static int ch341_set_handshake(struct usb_device *dev, u8 control) static int ch341_get_status(struct usb_device *dev, struct ch341_private *priv) { - char *buffer; + unsigned char *buffer; int r; -

Re: [PATCH v4 01/13] USB: ch341: fix error handling on resume

On 2016-04-29 14:16, Johan Hovold wrote: On Fri, Apr 15, 2016 at 11:14:04PM +0200, Grigori Goronzy wrote: This may fail, do not assume it always works. Signed-off-by: Grigori Goronzy --- drivers/usb/serial/ch341.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)

Re: [PATCH v4 12/13] USB: ch341: get rid of default configuration

On Fri, Apr 15, 2016 at 11:14:15PM +0200, Grigori Goronzy wrote: > If the serial port hasn't been opened yet, no baud rate should be > set and RTS/DTR need to be deasserted. But what about reset_resume? Thanks, Johan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the

Re: [PATCH v4 13/13] USB: ch341: implement tx_empty callback

On Fri, Apr 15, 2016 at 11:14:16PM +0200, Grigori Goronzy wrote: > The status bit was found with USB captures of the Windows driver and > some luck. Tested on CH340G and CH341A. > > v2: unify general status definitions > > Signed-off-by: Grigori Goronzy Looks good too.

Re: [PATCH v4 11/13] USB: ch341: improve B0 handling

On Fri, Apr 15, 2016 at 11:14:14PM +0200, Grigori Goronzy wrote: > Check for B0 in a more idiomatic way and make sure to not enable > RTS/CTS hardware flow control in B0 as it may override the control > lines. Also make sure to only enable RTS/DTR if there's a transition > from B0. Ah, here it

Re: [PATCH v4 10/13] USB: ch341: clean up messages

On Fri, Apr 15, 2016 at 11:14:13PM +0200, Grigori Goronzy wrote: > No functional change. Remove explicit function name printing, it's > easy to use dynamic debug to print it every time, if required. While that is true, we currently use __func__ in a lot of debug messages as a compact form for a

Re: [PATCHv3] usb: Add driver for UCSI

Hi Greg, On Thu, Apr 28, 2016 at 12:53:24PM -0700, Greg Kroah-Hartman wrote: > On Thu, Apr 21, 2016 at 03:43:40PM +0300, Heikki Krogerus wrote: > > USB Type-C Connector System Software Interface (UCSI) is > > specification that defines the registers and data structures > > that can be used to

Re: [PATCH v4 09/13] USB: ch341: fix coding style

On Fri, Apr 15, 2016 at 11:14:12PM +0200, Grigori Goronzy wrote: > No functional change. The following adjustments were made to be more in > line with official coding style and to be more consistent. > > Stop mixing tabs and spaces for alignment. Stop putting labels and > statements into the

Re: [PATCH v4 08/13] USB: ch341: add support for RTS/CTS flow control

On Fri, Apr 15, 2016 at 11:14:11PM +0200, Grigori Goronzy wrote: No commit message? > v2: use correct flag variable. > v3: fix compilation > > Signed-off-by: Grigori Goronzy > --- > drivers/usb/serial/ch341.c | 11 +++ > 1 file changed, 11 insertions(+) > > diff

Re: [PATCH v4 07/13] USB: ch341: add debug output for chip version

On Fri, Apr 15, 2016 at 11:14:10PM +0200, Grigori Goronzy wrote: > There are at least two hardware revisions, this may be helpful in > case compatibility issues need to be debugged. > > Signed-off-by: Grigori Goronzy > --- > drivers/usb/serial/ch341.c | 1 + > 1 file changed,

Re: [PATCH v4 06/13] USB: ch341: add support for parity, frame length, stop bits

On Fri, Apr 15, 2016 at 11:14:09PM +0200, Grigori Goronzy wrote: > With the new reinitialization method, configuring parity, different > frame lengths and different stop bit settings work as expected on > both CH340G and CH341A. This has been extensively tested with a > logic analyzer. > > v2:

Re: [PATCH v4 05/13] USB: ch341: reinitialize chip on reconfiguration

On Fri, Apr 15, 2016 at 11:14:08PM +0200, Grigori Goronzy wrote: > Changing the LCR register after initialization does not seem to be > reliable on all chips (particularly not on CH341A). Restructure > initialization and configuration to always reinit the chip on > configuration changes instead

Re: [PATCH 2/8] staging: rtl8192u: check return value eprom_read

On Thu, Apr 28, 2016 at 06:53:14PM +0100, Salah Triki wrote: > The call of eprom_read may fail, therefore its return value must be > checked. > > Signed-off-by: Salah Triki > --- > drivers/staging/rtl8192u/r8192U_core.c | 147 > +++-- > 1 file

Re: [PATCH v4 04/13] USB: ch341: fix USB buffer allocations

On Fri, Apr 15, 2016 at 11:14:07PM +0200, Grigori Goronzy wrote: > Use the correct types and sizes. > > v2: use u8 shorthand for unsigned char. Pleas place commit logs below the cut-off line (---). > Signed-off-by: Grigori Goronzy > --- > drivers/usb/serial/ch341.c | 10

Re: [PATCH 1/2] usb: chipidea: add flag CI_HDRC_DP_ALWAYS_PULLUP

Hello Peter, On 16-04-27 13:41:35, Peter Chen wrote: > On Wed, Apr 27, 2016 at 10:20:53AM +0530, maitysancha...@gmail.com wrote: > > > > > > Do you know the connect/disconnect by using USB Cable (not ID cable), I > > > just want to know if the software can know connection, > > > > I did not

Re: [PATCH v4 03/13] USB: ch341: add definitions for modem control

On Fri, Apr 15, 2016 at 11:14:06PM +0200, Grigori Goronzy wrote: No commit message? > Signed-off-by: Grigori Goronzy > --- > drivers/usb/serial/ch341.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/usb/serial/ch341.c

Re: [PATCH v4 02/13] USB: ch341: add LCR register definitions

On Fri, Apr 15, 2016 at 11:14:05PM +0200, Grigori Goronzy wrote: > BREAK2 seems to be a misnomer, the register configures various aspects > of the UART configuration. > > Signed-off-by: Grigori Goronzy Finally. Thanks for fixing this. :) Johan -- To unsubscribe from this

Re: [PATCH v4 01/13] USB: ch341: fix error handling on resume

On Fri, Apr 15, 2016 at 11:14:04PM +0200, Grigori Goronzy wrote: > This may fail, do not assume it always works. > > Signed-off-by: Grigori Goronzy > --- > drivers/usb/serial/ch341.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git

Re: dwc3+xhci in ARM64 issue

Hi, Joao Pinto writes: > Hi Felipe, > I confirmed that no interrupts are received. My hw colleague is going to check > the design! > > On 4/29/2016 11:25 AM, Felipe Balbi wrote: >> >> Hi João, >> >> Joao Pinto writes: >>> I am trying to bring

Re: [PATCH] usb: gadget: f_fs: Fix kernel panic for SuperSpeed

Hi, Jim Lin writes: > On 2016年04月28日 20:21, Felipe Balbi wrote: >>> >>> I also attach git log of system/core/adb/usb_linux_client.cpp of Android >>> N for your reference. >>> " >>> Author: Badhri Jagan Sridharan >>> Date: Mon Oct 5 13:04:03 2015 -0700 >>>

Re: [RFT PATCH 1/3] usb: misc: usb3503: Fix HUB mode after bootloader initialization

On 04/29/2016 01:30 PM, Mark Brown wrote: > On Fri, Apr 29, 2016 at 12:59:49PM +0200, Krzysztof Kozlowski wrote: > >> +++ b/Documentation/devicetree/bindings/usb/usb3503.txt >> @@ -24,6 +24,7 @@ Optional properties: >> pins (optional, if not provided, driver will not set rate of the >>

[PATCH] usbip: vudc: make dev_desc attribute binary

From: Igor Kotrasinski We read a struct usb_device_descriptor from it, so make it an actual binary attribute. Signed-off-by: Igor Kotrasinski Signed-off-by: Krzysztof Opasiak Tested-by: Krzysztof Opasiak

Applied "regulator: max77686: Configure enable time to properly handle regulator enable" to the regulator tree

The patch regulator: max77686: Configure enable time to properly handle regulator enable has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually

Re: [RFT PATCH 1/3] usb: misc: usb3503: Fix HUB mode after bootloader initialization

On Fri, Apr 29, 2016 at 12:59:49PM +0200, Krzysztof Kozlowski wrote: > +++ b/Documentation/devicetree/bindings/usb/usb3503.txt > @@ -24,6 +24,7 @@ Optional properties: > pins (optional, if not provided, driver will not set rate of the > REFCLK signal and assume that a value from the

Re: [PATCH] usb: gadget: f_fs: Fix kernel panic for SuperSpeed

On 2016年04月28日 20:21, Felipe Balbi wrote: I also attach git log of system/core/adb/usb_linux_client.cpp of Android N for your reference. " Author: Badhri Jagan Sridharan Date: Mon Oct 5 13:04:03 2015 -0700 adbd: Add os descriptor support for adb. Eventhough

[RFT PATCH 2/3] ARM: dts: exynos: Provide regulator for usb3503 on Odroid to fix device detection

On Odroid U3 (Exynos4412-based) board if USB was initialized by bootloader (in U-Boot "usb start" before tftpboot), the HUB after successful probing was not visible in the system ("lsusb"). Connected devices were not visible neither. The USB3503 takes optional regulator so provide one - buck8 on

[RFT PATCH 1/3] usb: misc: usb3503: Fix HUB mode after bootloader initialization

On Odroid U3 (Exynos4412-based) board if USB was initialized by bootloader (in U-Boot "usb start" before tftpboot), the HUB after after successful probing was not visible in the system ("lsusb"). Connected devices were not visible neither. In such case the USB3503 has to be fully reset before

[RFT PATCH 0/3] usb: misc: usb3503: Fix missing device when TFTP booting

Hi, Patches are independent, please pick up as you wish. However all of them are needed to solve the issue, so I am sending everything together for easier testng. Problem === When Odroid U3 (usb3503 + smsc95xx + max77686) boots from network (TFTP), the usb3503 does not show up in "lsusb".

[PATCH 3/3] regulator: max77686: Configure enable time to properly handle regulator enable

The enable time for buck regulators was not configured but actually is essential: consumers, like usb3503, doing hard reset (regulator off/on) should wait for the regulator to settle. Configure the enable time according to datasheet. Signed-off-by: Krzysztof Kozlowski

[PATCH] usb: usbip: Avoid NULL pointer dereference in case of error

One line above we have checked that udc is NULL so we shouldn't dereference it while printing error message. Reported-by: Dan Carpenter Signed-off-by: Krzysztof Opasiak --- drivers/usb/usbip/vudc_sysfs.c |2 +- 1 file changed, 1

Re: dwc3+xhci in ARM64 issue

Hi Felipe, I confirmed that no interrupts are received. My hw colleague is going to check the design! On 4/29/2016 11:25 AM, Felipe Balbi wrote: > > Hi João, > > Joao Pinto writes: >> I am trying to bring up a USB 3.0 Host Controller with an ARM64 platform >> (Juno)

Re: dwc3+xhci in ARM64 issue

Hi João, Joao Pinto writes: > I am trying to bring up a USB 3.0 Host Controller with an ARM64 platform > (Juno) > and I was also getting the dma issue discussed in this thread: > > https://www.mail-archive.com/linux-usb@vger.kernel.org/msg73137.html > > I then applied

dwc3+xhci in ARM64 issue

Hi Felipe, I am trying to bring up a USB 3.0 Host Controller with an ARM64 platform (Juno) and I was also getting the dma issue discussed in this thread: https://www.mail-archive.com/linux-usb@vger.kernel.org/msg73137.html I then applied Grygorii Strashko' patch and managed to have a bus

Re: [PATCH] Add DCD line support to CP210x driver

On Thu, Mar 24, 2016 at 10:53:27AM +0300, Valentin Yakovenkov wrote: > Sorry, I missed the branch. > > Here it is. Thanks for the patch. Please resubmit it on a format that can be applied (i.e. without quoted text, etc). Remember to include a patch revision in the Subject when resubmitting

Re: [PATCH V4] phy: bcm-ns-usb2: new driver for USB 2.0 PHY on Northstar

On Thursday 14 April 2016 03:07 PM, Rafał Miłecki wrote: > Northstar is a family of SoCs used in home routers. They have USB 2.0 > and 3.0 controllers with PHYs that need to be properly initialized. > This driver provides PHY init support in a generic way and can be bound > with an EHCI

Re: [PATCH V4] phy: bcm-ns-usb2: new driver for USB 2.0 PHY on Northstar

On Thursday 14 April 2016 03:07 PM, Rafał Miłecki wrote: > Northstar is a family of SoCs used in home routers. They have USB 2.0 > and 3.0 controllers with PHYs that need to be properly initialized. > This driver provides PHY init support in a generic way and can be bound > with an EHCI

Re: usbip: vudc: Add SysFS infrastructure for VUDC

On 04/29/2016 11:02 AM, Dan Carpenter wrote: > Hello Igor Kotrasinski, > > The patch ea6873a45a22: "usbip: vudc: Add SysFS infrastructure for > VUDC" from Mar 8, 2016, leads to the following static checker warning: > > drivers/usb/usbip/vudc_sysfs.c:201 usbip_status_show() > error:

Re: [PATCH v2] USB: Add uPD78F0730 USB to Serial Adaptor Driver

On Tue, Apr 26, 2016 at 03:24:53PM +0300, Maksim Salau wrote: > Hi Johan, > > On Sun, 24 Apr 2016 15:36:35 +0200 > Johan Hovold wrote: > > > On Mon, Feb 29, 2016 at 04:11:20PM +0300, Maksim Salau wrote: > > > The adaptor can be found on development boards for 78k, RL78 and

re: usbip: vudc: Add SysFS infrastructure for VUDC

Hello Igor Kotrasinski, The patch ea6873a45a22: "usbip: vudc: Add SysFS infrastructure for VUDC" from Mar 8, 2016, leads to the following static checker warning: drivers/usb/usbip/vudc_sysfs.c:201 usbip_status_show() error: we previously assumed 'udc' could be null (see line 200)

Re: usbip: vudc: Add VUDC main file

Ahh.. Too bad. Thanks for looking at this. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH v2] option.c: Support for Gemalto's Cinterion PH8 and AHxx products added

Added support for Gemalto's Cinterion PH8 and AHxx products with 2 RmNet Interfaces and products with 1 RmNet + 1 USB Audio interface. In addition some minor renaming and formatting. Signed-off-by: Hans-Christoph Schemmel --- Changes in v2: - using

Re: usbip: vudc: Add VUDC main file

On 04/28/2016 09:21 PM, Dan Carpenter wrote: > Hello Igor Kotrasinski, > > The patch 80fd9cd52de6: "usbip: vudc: Add VUDC main file" from Mar 8, > 2016, leads to the following static checker warning: > > drivers/usb/usbip/vudc_main.c:88 init() > warn: perhaps platform_device_put()

[PATCH v5] kconfig/symbol.c: handle choice_values that depend on 'm' symbols

If choices consist of choice_values of type tristate that depend on symbols set to 'm', those choice_values are not set to 'n' if the choice is changed from 'm' to 'y' (in which case only one active choice_value is allowed). Those values are also written to the config file causing modules to be

Re: [PATCH] usbip: vudc: fix Kconfig dependencies

Hi, On 04/28/2016 02:42 PM, Arnd Bergmann wrote: > With the addition of VUDC, the USBIP stack can now be used on > configurations without USB host support, but trying to build Not exactly. This is the goal but unfortunately for now this will not work... Most of USB_IP common functions operates

[GIT PULL] USB-serial fixes for v4.6-rc6

Hi Greg, Here are some new device ids for rc6. These have been in next for a few days now without any issues. Thanks, Johan The following changes since commit c3b46c73264b03000d1e18b22f5caf63332547c9: Linux 4.6-rc4 (2016-04-17 19:13:32 -0700) are available in the git repository at:

[PATCH] net/smscx5xx: use the device tree for mac address

From: Arnd Bergmann This takes the MAC address for smsc75xx/smsc95xx USB network devices from a the device tree. This is required to get a usable persistent address on the popular beagleboard, whose hardware designers accidentally forgot that an ethernet device really requires an

[PATCH v7 3/7] usb: mux: add driver for Intel gpio controlled port mux

In some Intel platforms, a single usb port is shared between USB host and device controller. The shared port is under control of GPIO pins. This patch adds the support for USB GPIO controlled port mux. [baolu: removed .owner per platform_no_drv_owner.cocci] Signed-off-by: David Cohen

[PATCH v7 0/7] usb: add support for Intel dual role port mux

Intel SOC chips are featured with USB dual role. The host role is provided by Intel xHCI IP, and the gadget role is provided by IP from designware. Tablet platform designs always share a single port for both host and gadget controllers. There is a mux to switch the port to the right controller

[PATCH v7 1/7] regulator: fixed: add support for ACPI interface

Add support to retrieve fixed voltage configure information through ACPI interface. This is needed for Intel Bay Trail devices, where a GPIO is used to control the USB vbus. Signed-off-by: Lu Baolu --- drivers/regulator/fixed.c | 46

[PATCH v7 5/7] mfd: intel_vuport: Add Intel virtual USB port MFD Driver

Some Intel platforms have an USB port mux controlled by GPIOs. There's a single ACPI platform device that provides 1) USB ID extcon device; 2) USB vbus regulator device; and 3) USB port switch device. This MFD driver will split these 3 devices for their respective drivers. [baolu: removed .owner

[PATCH v7 2/7] usb: mux: add generic code for dual role port mux

Several Intel platforms implement USB dual role by having completely separate xHCI and dwc3 IPs in PCH or SOC silicons. These two IPs share a single USB port. There is another external port mux which controls where the data lines should go. While the USB controllers are part of the silicon, the

[PATCH v7 6/7] usb: pci-quirks: add Intel USB drcfg mux device

In some Intel platforms, a single usb port is shared between USB host and device controllers. The shared port is under control of a switch which is defined in the Intel vendor defined extended capability for xHCI. This patch adds the support to detect and create the platform device for the port

[PATCH v7 4/7] usb: mux: add driver for Intel drcfg controlled port mux

Several Intel PCHs and SOCs have an internal mux that is used to share one USB port between device controller and host controller. The mux is handled through the Dual Role Configuration Register. Signed-off-by: Heikki Krogerus Signed-off-by: Lu Baolu

[PATCH v7 7/7] MAINTAINERS: add maintainer entry for Intel USB dual role mux drivers

Add a maintainer entry for Intel USB dual role mux drivers and add myself as a maintainer. Signed-off-by: Lu Baolu --- MAINTAINERS | 10 ++ 1 file changed, 10 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 1d5b4be..682c8a5 100644 --- a/MAINTAINERS

Re: [GIT PULL] USB: changes for v4.7 merge window

Hi, Greg Kroah-Hartman writes: > On Thu, Apr 28, 2016 at 01:46:03PM +0300, Felipe Balbi wrote: >> >> Hi Greg, >> >> here's the gadget pull request for v4.7 merge window. It's mostly dwc3 >> this time: >> >> $ git diff --dirstat v4.6-rc3 >> 74.4%

Re: [PATCH] usb: dwc3: usb/dwc3: fake dissconnect event when turn off pullup

Hi, John Youn writes: >> "Du, Changbin" writes: >>> Hi, Balbi, >>> >>> The step to reproduce this issue is: >>> 1) connect device to a host and wait its enumeration. >>> 2) trigger software disconnect by calling function >>>

Re: [PATCH 1/2] usb: dwc3: gadget: update DCFG.NumP to max burst size

Hi, John Youn writes: > On 4/28/2016 1:01 AM, Felipe Balbi wrote: >> NumP field of DCFG register is used on NumP field of >> ACK TP header and it tells the host how many packets >> an endpoint can receive before waiting for >> synchronization. >> >> Documentation says