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

2016-10-07 Thread Felipe Balbi
Hi, Michael Niewöhner writes: >> The clocks are same across working/non-working. >> Is it possible to bisect the commit that's causing hang for 4.8x ? > > > [c499ff71ff2a281366c6ec7a904c547d806cbcd1] usb: dwc3: core: re-factor init > and exit paths > This patch causes both the hang on reboot an

Re: [PATCH] extcon: usb-gpio: Add VBUS detection support

2016-10-07 Thread Roger Quadros
Hi Chanwoo, On 27/09/16 08:48, Peter Chen wrote: > On Tue, Sep 20, 2016 at 05:53:55PM +0300, Roger Quadros wrote: >> Driver can now work with both ID and VBUS pins or either one of >> them. >> >> There can be the following 3 cases >> >> 1) Both ID and VBUS GPIOs are available: >> >> ID = LOW -> U

Fwd: HSO driver patch

2016-10-07 Thread Matej Kupljen
Hi, I tried contacting authors of the driver mentioned in the source file and also in the MAINTAINERS file, but haven't received any reply so I am sending this to this mailing list. If I should use another one, plese advise me which one. Thanks and BR, Matej -- Forwarded message ---

Re: PROBLEM: am3517 usb-ohci not working

2016-10-07 Thread Łukasz Pułka
> Sounds like you're pretty close, in addition to the > pin muxing and PHY configuration, check also that you > have proper VBUS coming to the ports. Thank you. It was hardware problem Finally I received the schematics of the PHY connection from the board vendor. Suspend pin of PHY was pulled up

Re: Fwd: HSO driver patch

2016-10-07 Thread Oliver Neukum
On Fri, 2016-10-07 at 12:06 +0200, Matej Kupljen wrote: > Hi, > > I tried contacting authors of the driver mentioned in the source file > and also in the MAINTAINERS file, > but haven't received any reply so I am sending this to this mailing > list. If I should use another one, > plese advise me w

Re: Fwd: HSO driver patch

2016-10-07 Thread Matej Kupljen
Hi Oliver, tank you for quick response. >> I tried contacting authors of the driver mentioned in the source file >> and also in the MAINTAINERS file, >> but haven't received any reply so I am sending this to this mailing >> list. If I should use another one, >> plese advise me which one. > > Hi,

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

2016-10-07 Thread Johan Hovold
On Thu, Sep 15, 2016 at 04:57:34PM +0100, Aidan Thornton 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 and

Re: Fwd: HSO driver patch

2016-10-07 Thread Oliver Neukum
On Fri, 2016-10-07 at 12:47 +0200, Matej Kupljen wrote: Hi, > And my mail responded with: > > Delivery to the following recipient failed permanently: > > j.du...@option.com > > > How to proceed, please advise. ask somebody else @option about Jon and let's see whether he reads this list.

Re: Fwd: HSO driver patch

2016-10-07 Thread Greg KH
On Fri, Oct 07, 2016 at 12:06:54PM +0200, Matej Kupljen wrote: > Hi, > > I tried contacting authors of the driver mentioned in the source file > and also in the MAINTAINERS file, > but haven't received any reply so I am sending this to this mailing > list. If I should use another one, > plese advi

Re: PROBLEM: am3517 usb-ohci not working

2016-10-07 Thread Tony Lindgren
* Łukasz Pułka [161007 03:14]: > > Sounds like you're pretty close, in addition to the > > pin muxing and PHY configuration, check also that you > > have proper VBUS coming to the ports. > > Thank you. It was hardware problem > Finally I received the schematics of the PHY connection from the boa

Re: Fwd: HSO driver patch

2016-10-07 Thread Matej Kupljen
Hi, >> I tried contacting authors of the driver mentioned in the source file >> and also in the MAINTAINERS file, >> but haven't received any reply so I am sending this to this mailing >> list. If I should use another one, >> plese advise me which one. > > Can you use the scripts/get_maintainer.pl

Re: Fwd: HSO driver patch

2016-10-07 Thread Greg KH
On Fri, Oct 07, 2016 at 03:55:03PM +0200, Matej Kupljen wrote: > Hi, > > >> I tried contacting authors of the driver mentioned in the source file > >> and also in the MAINTAINERS file, > >> but haven't received any reply so I am sending this to this mailing > >> list. If I should use another one,

HSO driver patch [1/2]

2016-10-07 Thread Matej Kupljen
Hi, I am using hso driver for my 3G modem (although different manufacturer with different USB VID/PID) but I have some problems with it. It is working fine, but if you disconnect the USB connection while the data is transferring trough AT interface, we get a crash. There are two patches: 1.) 00

Re: HSO driver patch [2/2]

2016-10-07 Thread Matej Kupljen
Hi, second patch.. Thanks, Matej From 95cfca26bbcbb021e9327c03f8edf2ed0878de75 Mon Sep 17 00:00:00 2001 From: Matej Kupljen Date: Wed, 5 Oct 2016 13:08:31 +0200 Subject: [PATCH] Stop also serial queue when device is unplugged We need to also stop serial port when the device is unplugged, the ne

Re: HSO driver patch [1/2]

2016-10-07 Thread Greg KH
On Fri, Oct 07, 2016 at 04:29:42PM +0200, Matej Kupljen wrote: > Hi, > > > I am using hso driver for my 3G modem (although different manufacturer > with different USB VID/PID) but I have some problems with it. It is > working fine, but if you disconnect the USB connection while the data > is tran

HSO driver patch again [2/2]

2016-10-07 Thread Matej Kupljen
Hi, second patch: 0002-Stop-also-serial-queue-when-device-is-unplugged.patch Serial device was not stopped when the device got unplugged so there are continues error messages that the URB cannot be submitted. Thanks, Matej From: Matej Kupljen Date: Wed, 5 Oct 2016 13:08:31 +0200 Subject: [PATCH

HSO driver patch again [1/2]

2016-10-07 Thread Matej Kupljen
Hi, I am using hso driver for my 3G modem (although different manufacturer with different USB VID/PID) but I have some problems with it. It is working fine, but if you disconnect the USB connection while the data is transferring trough AT interface, we get a crash. First patch 0001-Reverse-the-or

Re: [PATCH v6 1/1] USB: serial: cp210x: Adding GPIO support for CP2105

2016-10-07 Thread Martyn Welch
On Tue, Oct 04, 2016 at 02:13:26PM +0200, Linus Walleij wrote: > On Sat, Sep 24, 2016 at 12:50 AM, Martyn Welch > wrote: > > > This patch adds support for the GPIO found on the CP2105. > > > > This device supports either push-pull or open-drain modes, it doesn't > > provide an explicit input mo

Re: [PATCH v2] hid: hid-led: fix issue with transfer buffer not being dma capable

2016-10-07 Thread Benjamin Tissoires
On Oct 03 2016 or thereabouts, Heiner Kallweit wrote: > The hid-led driver works fine under 4.8.0, however with the next > kernel from today I get this: > > [ cut here ] > WARNING: CPU: 0 PID: 2578 at drivers/usb/core/hcd.c:1584 > usb_hcd_map_urb_for_dma+0x373/0x550 [usbco

[PATCH/RFT 05/12] USB: ohci-da8xx: Fix probe for devices with no vbus/oci gpio

2016-10-07 Thread ahaslam
From: Axel Haslam Some boards dont have gpios assigened for vbus or oci. Allow these boards to enumerate usb without declaring the set_power and/or the ocic_notify callbacks in platform data. Signed-off-by: Axel Haslam --- drivers/usb/host/ohci-da8xx.c | 8 +--- 1 file changed, 5 insertio

[PATCH/RFT 08/12] ARM: davinci: register the usb20_phy clock on the SoC file

2016-10-07 Thread ahaslam
From: Axel Haslam The usb20_phy clock needs to be registered for the driver to be able to get and enable a clock. Currently the usb phy clocks are registered form board files, which will not be called during a device tree based boot. To be able to probe correctly usb form a device tree boot, reg

[PATCH/RFT 03/12] ARM: davinci: rename root_hub to platform_data

2016-10-07 Thread ahaslam
From: Axel Haslam To prepare for DT support we will remove the usb callback function pointers. Since this structure will only pass data to the driver, It seems better to rename the structure root_hub structure to platform_data There is no functional change. Signed-off-by: Axel Haslam --- arch

[PATCH/RFT 10/12] USB: ohci-da8xx: Add device tree support

2016-10-07 Thread ahaslam
From: Axel Haslam This allows the controller to be specified via device tree. Signed-off-by: Axel Haslam --- drivers/usb/host/ohci-da8xx.c | 52 +-- 1 file changed, 50 insertions(+), 2 deletions(-) diff --git a/drivers/usb/host/ohci-da8xx.c b/drivers/us

[PATCH/RFT 04/12] USB: ohci-da8xx: Divide power up time in the ohci driver

2016-10-07 Thread ahaslam
From: Axel Haslam Instead of requiring platform data to know that the effective time should be diveded by two, Make that operation in the driver so that users (platform board files/Device tree) dont have to worry about it. Signed-off-by: Axel Haslam --- arch/arm/mach-davinci/board-da830-evm.c

[PATCH/RFT 09/12] usb: host: ohci-da8xx: Add devicetree bindings documentation

2016-10-07 Thread ahaslam
From: Axel Haslam This patch documents the device tree bindings required for the ohci controller found in TI da8xx family of SoC's Signed-off-by: Axel Haslam --- .../devicetree/bindings/usb/ohci-da8xx.txt | 32 ++ 1 file changed, 32 insertions(+) create mode 100644

[PATCH/RFT 02/12] ARM: davinci: hawk: add full constraints for ohci plat boot

2016-10-07 Thread ahaslam
From: Axel Haslam The phy framework requests an optional "phy" regulator. If it does not find one, it returns -EPROBE_DEFER. In the case of non-DT based boot for the omap138-lcdk board, this would prevent the usb11 phy to probe correctly and ohci would not enumerate. By calling "regulator_has_fu

[PATCH/RFT 07/12] USB: ohci-da8xx: Request gpios and handle interrupt in the driver

2016-10-07 Thread ahaslam
From: Axel Haslam Currently requesting the vbus and overcurrent gpio is handled on the board specific file. But this does not play well moving to device tree. In preparation to migrate to a device tree boot, handle requesting gpios and overcurrent interrupt on the usb driver itself, thus avoidin

[PATCH/RFT 12/12] ARM: dts: da850-lcdk: enable ohci usb

2016-10-07 Thread ahaslam
From: Axel Haslam This enables the ohci usb controller for the lcdk board. Signed-off-by: Axel Haslam --- arch/arm/boot/dts/da850-lcdk.dts | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm/boot/dts/da850-lcdk.dts b/arch/arm/boot/dts/da850-lcdk.dts index 7b8ab21..6da9d843 10

[PATCH/RFT 06/12] ARM: davinci: hawk: Remove oci and vbus gpios

2016-10-07 Thread ahaslam
From: Axel Haslam The omap138-lcdk and its predecessor the hawk board don't have gpios connected to control vbus or get the over current notifications for usb. for example, in the hawk board gpio6-13 is connected to a LED, and gpio2-4 is not connected at all. In the lcdk board, gpio 2-4 is a push

[PATCH/RFT 11/12] ARM: dts: da850: Add the usb ohci device node

2016-10-07 Thread ahaslam
From: Axel Haslam This adds the device tree node for the usb11 (ohci) controller present in the da850 family of SoC's. Signed-off-by: Axel Haslam --- arch/arm/boot/dts/da850.dtsi | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.

[PATCH/RFT 00/12] Add DT support for ohci-da8xx

2016-10-07 Thread ahaslam
From: Axel Haslam The purpose of this patch series is to add DT support to the ohci-da8xx glue driver without breaking the non-DT boot, which is still used in unconverted davinci devices. To Achieve this, the first 8 patches make sure that the non-DT based enumeration works, and prepares the sta

[PATCH/RFT 01/12] ARM: davinci: da8xx: Enable the usb20 "per" clk on phy_clk_enable

2016-10-07 Thread ahaslam
From: Axel Haslam While probing ochi phy with usb20 phy as a parent clock for usb11_phy, the usb20_phy clock enable would time out. This is because the usb20 module clock needs to enabled while trying to lock the usb20_phy PLL. Call clk enable and get for the usb20 peripheral before trying to en

Re: [PATCH v6 1/1] USB: serial: cp210x: Adding GPIO support for CP2105

2016-10-07 Thread Martyn Welch
On Fri, Oct 07, 2016 at 04:31:26PM +0100, Martyn Welch wrote: > Also, if an output can only be open-drain, attempting to set the pin as > push-pull succeeds because gpiolib (currently) assumes that a pin can > always be p-p and doesn't even check the return value of it's call to > .set_single_ended

Re: [PATCH/RFT 11/12] ARM: dts: da850: Add the usb ohci device node

2016-10-07 Thread Sergei Shtylyov
Hello. On 10/07/2016 07:42 PM, ahas...@baylibre.com wrote: From: Axel Haslam This adds the device tree node for the usb11 (ohci) controller present in the da850 family of SoC's. Signed-off-by: Axel Haslam --- arch/arm/boot/dts/da850.dtsi | 8 1 file changed, 8 insertions(+) diff

Re: [PATCH v2] hid: hid-led: fix issue with transfer buffer not being dma capable

2016-10-07 Thread Heiner Kallweit
Am 07.10.2016 um 18:22 schrieb Benjamin Tissoires: > On Oct 03 2016 or thereabouts, Heiner Kallweit wrote: >> The hid-led driver works fine under 4.8.0, however with the next >> kernel from today I get this: >> >> [ cut here ] >> WARNING: CPU: 0 PID: 2578 at drivers/usb/core

[PATCH] usb: dwc3: Fix size used in dma_free_coherent()

2016-10-07 Thread Christophe JAILLET
In commit 2abd9d5fa60f9 ("usb: dwc3: ep0: Add chained TRB support"), the size of the memory allocated with 'dma_alloc_coherent()' has been modified but the corresponding calls to 'dma_free_coherent()' have not been updated accordingly. This has been spotted with coccinelle, using the following scr

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

2016-10-07 Thread Michael Niewöhner
Hi Felipe, On Fr, 2016-10-07 at 10:42 +0300, Felipe Balbi wrote: > Hi, > > Michael Niewöhner writes: > > > > > > > > The clocks are same across working/non-working. > > > Is it possible to bisect the commit that's causing hang for 4.8x ? > > > > > > [c499ff71ff2a281366c6ec7a904c547d806cbcd1]

USB crash on BeagleBoard-xM

2016-10-07 Thread Snaper
Hi, This is on a BeagleBoard-xM with a fresh image from https://eewiki.net/display/linuxonarm/BeagleBoard. I attach the output of dmesg after booting. Some seconds after booting USB seems to crash, since the keyboard no longer works. The board seems to continue alive. The ethernet interfa

Re: [PATCH] usb: dwc3: host: inherit dma configuration from parent dev

2016-10-07 Thread Leo Li
On Thu, Sep 22, 2016 at 12:02 AM, Sriram Dash wrote: >>From: Arnd Bergmann [mailto:a...@arndb.de] >>On Wednesday, September 21, 2016 11:43:59 AM CEST Sriram Dash wrote: >>> >From: Arnd Bergmann [mailto:a...@arndb.de] On Wednesday, September >>> >21, 2016 11:06:47 AM CEST Sriram Dash wrote: >>> >>>

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

2016-10-07 Thread Baolin Wang
Hi Neil, On 5 October 2016 at 18:44, NeilBrown wrote: > On Wed, Oct 05 2016, Felipe Balbi wrote: > >> Hi Baolin, >> >> Baolin Wang writes: > But you do! > The mA number from the USB configuration is passed to > usb_gadget_vbus_draw. > Your patch passes that to usb_charger_set_cu