Re: [PATCH v2 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx

On Thursday 03 November 2016 09:33 PM, Axel Haslam wrote: > The ohci device name has changed in the board configuraion files, > hence, change the phy lookup table to match the new name. > > Signed-off-by: Axel Haslam merged, thanks. -Kishon > --- >

[PATCH] USB: serial: ftdi_sio: add support for TI CC3200 LaunchPad

This patch adds support for the TI CC3200 LaunchPad board, which uses a custom USB vendor ID and product ID. Channel A is used for JTAG, and channel B is used for a UART. Signed-off-by: Doug Brown --- drivers/usb/serial/ftdi_sio.c | 2 ++

Re: [PATCH] usb: dwc2: gadget: Update for new usb_endpoint_maxp()

On 11/1/2016 4:14 AM, Felipe Balbi wrote: > > Hi, > > John Youn writes: >> From: Vardan Mikayelyan >> >> Update the dwc2 driver for the new behavior of the usb_endpoint_maxp() >> and also use the new usb_endpoint_maxp_mult() helper function. >> >>

Re: [PATCH 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx

On Friday 04 November 2016 11:04 AM, Sekhar Nori wrote: > Hi Kishon, > > On Thursday 03 November 2016 10:20 PM, Kishon Vijay Abraham I wrote: >> >> >> On Wednesday 02 November 2016 06:14 PM, Axel Haslam wrote: >>> There is only one ohci on the da8xx series of chips, >>> so remove the ".0" when

Re: [PATCH v5 02/23] of: device: Export of_device_{get_modalias, uvent_modalias} to modules

Quoting Peter Chen (2016-10-24 18:16:32) > On Mon, Oct 24, 2016 at 12:48:24PM -0700, Stephen Boyd wrote: > > Quoting Chen-Yu Tsai (2016-10-24 05:19:05) > > > Hi, > > > > > > On Tue, Oct 18, 2016 at 9:56 AM, Stephen Boyd > > > wrote: > > > > The ULPI bus can be built as

Re: [PATCH v4 3/4] usb: musb: Add a quirk flag to skip the phy set mode

Hello. On 11/04/2016 07:43 PM, Alexandre Bailon wrote: During the init, the driver will use the mode to configure the controller mode and the phy mode. PHY -- be consistent please... The PHY of DA8xx has some issues when the phy is forced in host or device. Again. Add way to skip

Re: [PATCH v4 3/4] usb: musb: Add a quirk flag to skip the phy set mode

On 11/04/2016 11:43 AM, Alexandre Bailon wrote: During the init, the driver will use the mode to configure the controller mode and the phy mode. The PHY of DA8xx has some issues when the phy is forced in host or device. Add way to skip the set mode and let the da8xx glue manage the phy mode.

Re: [PATCH v2 3/5] usb: dwc3: gadget: Write the event count in interrupt

On 11/4/2016 2:13 AM, Janusz Dziedzic wrote: > On 4 November 2016 at 07:41, Janusz Dziedzic > wrote: >> On 4 November 2016 at 02:31, John Youn wrote: >>> >>> Since we are saving the event count and handling the events in the >>> threaded

Re: [PATCH 0/2] musb-fixes for v4.9-rc2

On Fri, Nov 04, 2016 at 07:48:13AM -0700, Tony Lindgren wrote: > * Ladislav Michl [161104 03:41]: > > All your patches on top of current Linus' git and revert of: > > commit 87326e858448c40e32f142c0b8dcc59d7b27c641 > > Author: Tony Lindgren > > Date: Tue

[PATCH v4 3/4] usb: musb: Add a quirk flag to skip the phy set mode

During the init, the driver will use the mode to configure the controller mode and the phy mode. The PHY of DA8xx has some issues when the phy is forced in host or device. Add way to skip the set mode and let the da8xx glue manage the phy mode. Signed-off-by: Alexandre Bailon

[PATCH v4 2/4] phy: da8xx-usb: Configure CFGCHIP2 to support OTG workaround

If we configure the da8xx OTG phy in OTG mode, neither device or host mode will work. That is because the PHY is not able to detect and notify the driver that value of ID pin changed. To work despite this hardware limitation, the da8xx glue implement a workaround. But to work, the workaround

[PATCH v4 1/4] usb: musb: da8xx: Call earlier clk_prepare_enable()

The first attempt to read a register may fail because the clock may not be enabled, and then the probe of musb driver will fail. Call clk_prepare_enable() before the first register read. Signed-off-by: Alexandre Bailon --- drivers/usb/musb/da8xx.c | 17 - 1

[PATCH v4 4/4] usb: musb: da8xx: Set phy in OTG mode by default

The DA8xx OTG PHY has some issues when it is forced in host or peripheral mode. Actually, most of the time, OTG is the best mode because host or peripheral mode are only required for hardware that miss some circuitry. Init the PHY mode OTG mode by default. Signed-off-by: Alexandre Bailon

[PATCH v4 0/4] usb: musb: da8xx: Fix few issues

Currently, the USB OTG of the da8xx doesn't work. This series intend to fix them. Change in v2: * Fix the error path da8xx_musb_init() Changes in v3: * Remove the host workaround that was not working on every platform * Add a property to the devicetree node of phy to force the phy in a specific

Re: musb RPM sleep-while-atomic in 4.9-rc1

* Johan Hovold [161104 07:16]: > On Thu, Nov 03, 2016 at 02:26:35PM -0700, Tony Lindgren wrote: > > OK. Sorry for the delay responding, had my motherboard fail > > over the weekend.. > > Ouch. Hope the recovery process wasn't too painful. Only the usual scratches on my

Re: [PATCH 0/2] musb-fixes for v4.9-rc2

* Ladislav Michl [161104 03:41]: > All your patches on top of current Linus' git and revert of: > commit 87326e858448c40e32f142c0b8dcc59d7b27c641 > Author: Tony Lindgren > Date: Tue May 31 10:05:20 2016 -0500 > > usb: musb: Remove extra PM runtime

Re: [PATCH 0/2] musb-fixes for v4.9-rc2

* Ladislav Michl [161104 02:47]: > On Fri, Nov 04, 2016 at 10:31:38AM +0200, Felipe Balbi wrote: > [snip] > > Sounds like VBUS dropping to me. Remember, MUSB is really anal about > > VBUS levels. If it drops enough for the PHY to report one of those 4 > > VBUS levels, then

[PATCH] USB: musb: remove obsolete resume-signalling comments

Remove comments about resume signalling being stopped from GetPortStatus, something which is no longer the case. Fixes: 8ed1fb790ea2 ("usb: musb: finish suspend/reset work...") Signed-off-by: Johan Hovold --- drivers/usb/musb/musb_core.c| 5 +

Re: musb RPM sleep-while-atomic in 4.9-rc1

On Thu, Nov 03, 2016 at 02:26:35PM -0700, Tony Lindgren wrote: > * Johan Hovold [161031 04:50]: > > On Fri, Oct 28, 2016 at 11:13:19AM -0700, Tony Lindgren wrote: > > > * Johan Hovold [161028 02:45]: > > > > On Thu, Oct 27, 2016 at 12:15:52PM -0700, Tony

Re: [PATCH] usbnet: prevent device rpm suspend in usbnet_probe function

On Fri, 4 Nov 2016, Kai-Heng Feng wrote: > Sometimes cdc_mbim failed to probe if runtime pm is enabled: > [9.305626] cdc_mbim: probe of 2-2:1.12 failed with error -22 > > This can be solved by increase its pm usage counter. This should not be needed. The USB core increments the PM usage

Re: [RFC PATCH] Fix auto-remount of safely removed or ejected USB-3 devices

On Fri, 4 Nov 2016, Mathias Nyman wrote: > Time to get this thing forward. > > Many USB-3 mass storage devices remount after "eject" or safe removal. > Windows solves this by setting the device to U3, and we will do the same. > This same info is all in the patch description. > > I am however

Re: [PATCH 1/1] usb: xhci: remove the use of xhci->addr_dev

On 02.11.2016 04:30, Lu Baolu wrote: xhci->addr_dev is used for the completion of both address device and enable slot commands. It's shared by enumerations of all USB devices connected to an xhci host. Hence, it's just a source for possible races. Since we've introduced command structure and the

[RFC PATCH] Fix auto-remount of safely removed or ejected USB-3 devices

Time to get this thing forward. Many USB-3 mass storage devices remount after "eject" or safe removal. Windows solves this by setting the device to U3, and we will do the same. This same info is all in the patch description. I am however touching the pm states of usb devices from usb core in

[RFC PATCH] usb: hub: Fix auto-remount of safely removed or ejected USB-3 devices

USB-3 does not have any link state that will avoid negotiating a connection with a plugged-in cable but will signal the host when the cable is unplugged. For USB-3 we used to first set the link to Disabled, then to RxDdetect to be able to detect cable connects or disconnects. But in RxDetect the

Re: [PATCH v3 3/5] dt/bindings: Add a new property to DA8xx USB PHY

On 11/03/2016 06:50 PM, Kishon Vijay Abraham I wrote: > Hi, > > On Thursday 03 November 2016 10:56 PM, Alexandre Bailon wrote: >> On 11/03/2016 05:34 PM, Kishon Vijay Abraham I wrote: >>> Hi, >>> >>> On Thursday 03 November 2016 08:56 PM, Alexandre Bailon wrote: The USB PHY is able to

Re: [PATCH 0/2] musb-fixes for v4.9-rc2

Hi Tony, On Thu, Nov 03, 2016 at 03:55:32PM -0700, Tony Lindgren wrote: > * Tony Lindgren [161103 13:59]: > > * Ladislav Michl [161101 14:14]: > > > > cacaaf80c3a6 ("usb: musb: Call pm_runtime from musb_gadget_queue") > > > > d8e5f0eca1e8 ("usb: musb: Fix

Re: [PATCH 0/2] musb-fixes for v4.9-rc2

On Fri, Nov 04, 2016 at 10:46:24AM +0100, Ladislav Michl wrote: > On Fri, Nov 04, 2016 at 10:31:38AM +0200, Felipe Balbi wrote: > [snip] > > Sounds like VBUS dropping to me. Remember, MUSB is really anal about > > VBUS levels. If it drops enough for the PHY to report one of those 4 > > VBUS

[PATCH] usbnet: prevent device rpm suspend in usbnet_probe function

Sometimes cdc_mbim failed to probe if runtime pm is enabled: [9.305626] cdc_mbim: probe of 2-2:1.12 failed with error -22 This can be solved by increase its pm usage counter. Signed-off-by: Kai-Heng Feng --- drivers/net/usb/usbnet.c | 7 ++- 1 file changed,

Re: [PATCH 0/2] musb-fixes for v4.9-rc2

On Fri, Nov 04, 2016 at 10:31:38AM +0200, Felipe Balbi wrote: [snip] > Sounds like VBUS dropping to me. Remember, MUSB is really anal about > VBUS levels. If it drops enough for the PHY to report one of those 4 > VBUS levels, then MUSB just gives up. > > What we used to do back at Nokia was

Re: [PATCH v2 3/5] usb: dwc3: gadget: Write the event count in interrupt

On 4 November 2016 at 07:41, Janusz Dziedzic wrote: > On 4 November 2016 at 02:31, John Youn wrote: >> >> Since we are saving the event count and handling the events in the >> threaded interrupt handler, we can write and clear out the eventcount

Re: [PATCH 0/2] musb-fixes for v4.9-rc2

Hi, Tony Lindgren writes: >> > * Tony Lindgren [161021 00:18]: >> > > * Ladislav Michl [161020 12:37]: >> > > > [ 186.457519] musb-hdrc musb-hdrc.0.auto: VBUS_ERROR in a_wait_bcon >> > > > (90,

Darlehen Angebot

Schönen Tag, Brauchen Sie eine persönliche oder geschäftliche Darlehen ohne Stress und schnelle Genehmigung? Wenn ja, kontaktieren Sie uns heute, wie wir derzeit bieten Darlehen zu hervorragenden Zinssatz. Unser Darlehen ist gesichert und sicher, unsere Kunden Glück ist unsere Stärke. Für

Re: [PATCH v2 3/5] usb: dwc3: gadget: Write the event count in interrupt

On 4 November 2016 at 02:31, John Youn wrote: > > Since we are saving the event count and handling the events in the > threaded interrupt handler, we can write and clear out the eventcount in > the hard interrupt handler itself. > > This behavior will be required for IP