Re: [PATCH v6 03/25] usb: ulpi: Support device discovery via DT

On Thu, Jan 19, 2017 at 02:33:49PM +0800, Peter Chen wrote: > On Wed, Dec 28, 2016 at 02:56:49PM -0800, 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

Re: [PATCH v6 03/25] usb: ulpi: Support device discovery via DT

On Wed, Dec 28, 2016 at 02:56:49PM -0800, 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 v6 23/25] usb: chipidea: Pullup D+ in device mode via phy APIs

On Wed, Jan 18, 2017 at 02:57:27PM -0600, Rob Herring wrote: > On Wed, Jan 18, 2017 at 2:54 PM, Stephen Boyd wrote: > > Quoting Peter Chen (2017-01-17 23:34:32) > >> On Tue, Jan 17, 2017 at 09:58:33AM -0800, Stephen Boyd wrote: > >> > Quoting Peter Chen (2017-01-15

Re: [PATCH 2/2] usb: musb: Size 1 dma in transfers won't complete with cpp41

On Wed, Jan 18, 2017 at 06:29:59PM -0800, Tony Lindgren wrote: > At least with the cppi41 dma, size 1 in dma transfers will just wait In which case do you see the size 1 transfer? using testusb? > until the device is disconnected. This causes timeouts in cppi41 dma > runtime PM. > > Also the

Re: [PATCH] usb: dwc3: core: Disable USB2.0 phy suspend when dwc3 acts as host role

Hi John, On 19 January 2017 at 11:31, John Youn wrote: > On 1/18/2017 7:12 PM, Baolin Wang wrote: >> Hi John, >> >> On 19 January 2017 at 09:33, John Youn wrote: >>> On 1/16/2017 2:38 AM, Felipe Balbi wrote: Hi, John Youn

Re: [PATCH] usb: dwc3: core: Disable USB2.0 phy suspend when dwc3 acts as host role

Hi John, On 19 January 2017 at 09:33, John Youn wrote: > On 1/16/2017 2:38 AM, Felipe Balbi wrote: >> >> Hi, >> >> John Youn writes: Baolin Wang writes: >> Baolin Wang writes: >>> When

Re: [PATCH] usb: dwc3: core: Disable USB2.0 phy suspend when dwc3 acts as host role

On 1/18/2017 7:12 PM, Baolin Wang wrote: > Hi John, > > On 19 January 2017 at 09:33, John Youn wrote: >> On 1/16/2017 2:38 AM, Felipe Balbi wrote: >>> >>> Hi, >>> >>> John Youn writes: > Baolin Wang writes: >>>

[PATCH 1/2] usb: musb: Fix host mode error -71 regression

Commit 467d5c980709 ("usb: musb: Implement session bit based runtime PM for musb-core") started implementing musb generic runtime PM support by introducing devctl register session bit based state control. This caused a regression where if a USB mass storage device is connected to a USB hub, we

[PATCH 2/2] usb: musb: Size 1 dma in transfers won't complete with cpp41

At least with the cppi41 dma, size 1 in dma transfers will just wait until the device is disconnected. This causes timeouts in cppi41 dma runtime PM. Also the initial size 8 transfers take about 200ms to complete when plugging a USB mass storage device to a hub. But we probably want to keep those

[PATCH 4/4] usb: dwc2: gadget: Add checking for g-tx-fifo-size parameter

From: Sevak Arakelyan Add dwc2_check_param_tx_fifo_sizes function which validates the members of g_tx_fifo_size array and sets to average or default values if it is needed. Cc: Stefan Wahren Signed-off-by: Sevak Arakelyan

[PATCH 3/4] usb: dwc2: gadget: Set TX FIFO depths to calculated defaults

From: Sevak Arakelyan Remove legacy DWC2_G_P_LEGACY_TX_FIFO_SIZE array for TX FIFOs. Update dwc2_set_param_tx_fifo_sizes function to calculate and assign default average FIFO depth to each member of g_tx_fifo_size array. Total FIFO size, EP Info block's size, FIFO operation

[PATCH 1/4] usb: dwc2: gadget: Set GDFIFOCFG

From: Sevak Arakelyan Add programming of GDFIFOCFG register in device mode. It must contain start address for EP Info block and total FIFO depth. Signed-off-by: Sevak Arakelyan Signed-off-by: John Youn ---

[PATCH 0/4] usb: dwc2: FIFO configuration

This series addresses a couple of FIFO issues in dwc2. The first it properly configures the GDIFIFOCFG registers in host/gadget mode. Next it configures the TX FIFOs to default values in gadget mode. These values should work for all cores. The old constant values were incorrect in some cases

[PATCH 2/4] usb: dwc2: host: Correct snpsid checking for GDFIFOCFG

From: Sevak Arakelyan GDFIFOCFG is available from IP version 2.91a. Fix the code to reflect this. Signed-off-by: Sevak Arakelyan Signed-off-by: John Youn --- drivers/usb/dwc2/core.h | 1 + drivers/usb/dwc2/hcd.c | 3 ++- 2

[PATCHv2 0/2] Two musb fixes for v4.10-rc cycle

Hi all, Here are two fixes for v4.10-rc cycle to deal with error -75 and -115 issues when plugging in USB mass storage device to a hub. Note that I will also post two cppi41 dma related patches, but those can be applied separately. Regards, Tony Changes since v1: - Handle in transfer quirk

Re: [PATCH] usb: dwc3: core: Disable USB2.0 phy suspend when dwc3 acts as host role

On 1/16/2017 2:38 AM, Felipe Balbi wrote: > > Hi, > > John Youn writes: >>> Baolin Wang writes: > Baolin Wang writes: >> When dwc3 controller acts as host role with attaching slow speed device >> (like mouse or

Re: [PATCH 2/2] usb: musb: Tiny dma in transfers won't complete with cpp41

* Tony Lindgren [170118 16:50]: > At least with the cppi41 dma, size 1 in dma transfers will just wait > until the device is disconnected. And it also seems that enumerating > a USB stick with a hub can take a USB reset with smallish size in > transfers. > > This causes

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

* Bin Liu [170118 13:14]: > On Wed, Jan 18, 2017 at 12:48:59PM -0800, Tony Lindgren wrote: > > And here's a fix for the error -71 regression. > > > > Bin, can you review and test your earlier case mentioned in > > commit 9298b4aad37e ("usb: musb: fix device hotplug behind hub")

[PATCH 2/2] usb: musb: Tiny dma in transfers won't complete with cpp41

At least with the cppi41 dma, size 1 in dma transfers will just wait until the device is disconnected. And it also seems that enumerating a USB stick with a hub can take a USB reset with smallish size in transfers. This causes timeouts in cppi41 dma runtime PM. Fix the issue by adding a minimum

[PATCH 0/2] Two musb fixes for v4.10-rc cycle

Hi all, Here are two fixes for v4.10-rc cycle to deal with error -75 and -115 issues when plugging in USB mass storage device to a hub. Note that I will also post two cppi41 dma related patches, but those can be applied separately. Regards, Tony Tony Lindgren (2): usb: musb: Fix host mode

[PATCH 1/2] usb: musb: Fix host mode error -71 regression

Commit 467d5c980709 ("usb: musb: Implement session bit based runtime PM for musb-core") started implementing musb generic runtime PM support by introducing devctl register session bit based state control. This caused a regression where if a USB mass storage device is connected to a USB hub, we

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

On Wed, Jan 18, 2017 at 12:48:59PM -0800, Tony Lindgren wrote: > * Bin Liu [170118 10:49]: > > On Wed, Jan 18, 2017 at 10:44:32AM -0800, Tony Lindgren wrote: > > > * Tony Lindgren [170118 10:15]: > > > > * Grygorii Strashko [170118

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

On 01/18/2017 12:15 PM, Tony Lindgren wrote: > * Grygorii Strashko [170118 10:05]: >> >> >> On 01/18/2017 10:53 AM, Tony Lindgren wrote: >>> Hi, >>> >>> * Bin Liu [170118 06:26]: With this v3, I still get -71 error when a device is plugged to a hub

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

On Wed, Jan 18, 2017 at 10:44:32AM -0800, Tony Lindgren wrote: > * Tony Lindgren [170118 10:15]: > > * Grygorii Strashko [170118 10:05]: > > > > > > > > > On 01/18/2017 10:53 AM, Tony Lindgren wrote: > > > > Hi, > > > > > > > > * Bin Liu

Re: [PATCH v6 23/25] usb: chipidea: Pullup D+ in device mode via phy APIs

Quoting Peter Chen (2017-01-17 23:34:32) > On Tue, Jan 17, 2017 at 09:58:33AM -0800, Stephen Boyd wrote: > > Quoting Peter Chen (2017-01-15 19:45:51) > > > > > > At include/linux/usb/phy.h, we have .set_vbus interface, maybe you need > > > to port it to generic phy framework. > > > > > > > Ok.

Re: [PATCH v6 23/25] usb: chipidea: Pullup D+ in device mode via phy APIs

On Wed, Jan 18, 2017 at 2:54 PM, Stephen Boyd wrote: > Quoting Peter Chen (2017-01-17 23:34:32) >> On Tue, Jan 17, 2017 at 09:58:33AM -0800, Stephen Boyd wrote: >> > Quoting Peter Chen (2017-01-15 19:45:51) >> > > >> > > At include/linux/usb/phy.h, we have .set_vbus

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

* Bin Liu [170118 10:49]: > On Wed, Jan 18, 2017 at 10:44:32AM -0800, Tony Lindgren wrote: > > * Tony Lindgren [170118 10:15]: > > > * Grygorii Strashko [170118 10:05]: > > > > > > > > > > > > On 01/18/2017 10:53 AM, Tony Lindgren

[PATCH] USB: qcserial: add Dell DW5570 QDL

The Dell DW5570 is a re-branded Sierra Wireless MC8805 which will by default boot with vid 0x413c and pid 0x81a3. When triggered QDL download mode, the device switches to pid 0x81a6 and provides the standard TTY used for firmware upgrade. Cc: Signed-off-by: Aleksander

Re: [RFC v2 1/5] UDC: Split the driver into amd (pci) and Synopsys core driver

On Wed, Jan 18, 2017 at 10:45:39AM -0800, Florian Fainelli wrote: > On 01/17/2017 12:05 AM, Raviteja Garimella wrote: > > This patch splits the amd5536udc driver into two -- one that does > > pci device registration and the other file that does the rest of > > the driver tasks like the gadget/ep

Re: [PATCH v2 1/2] dt-bindings: usb: add DT binding for s3c2410 USB device controller

On Wed, Jan 11, 2017 at 08:02:29PM -0200, Sergio Prado wrote: > Adds the device tree bindings description for Samsung S3C2410 and > compatible USB device controller. > > Signed-off-by: Sergio Prado > --- > .../devicetree/bindings/usb/s3c2410-usb.txt| 28 >

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

* Grygorii Strashko [170118 11:18]: > Just thinking, may be cppi41 should not be platform device at all > and it might be reasonable to have it as lib with > cppi41_init()/cppi41_remove(), > so musb SoC glue layer will initialize it, because it provides services to >

Re: [PATCH] usb: dwc2: remove dead function dwc2_pci_quirks

On 1/17/2017 12:51 PM, Heiner Kallweit wrote: > Commit 9962b62f1be9 "Deprecate g-use-dma binding" removed the only > property in dwc2_pci_quirks. This function is dead code now. > > Maybe it was kept intentionally to be prepared for the case that > another quirk-related property needs to be added

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

* Grygorii Strashko [170118 10:05]: > > > On 01/18/2017 10:53 AM, Tony Lindgren wrote: > > Hi, > > > > * Bin Liu [170118 06:26]: > >> With this v3, I still get -71 error when a device is plugged to a hub to > >> musb. It doesn't happen though if the

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

On Wed, Jan 18, 2017 at 08:53:09AM -0800, Tony Lindgren wrote: > Hi, > > * Bin Liu [170118 06:26]: > > With this v3, I still get -71 error when a device is plugged to a hub to > > musb. It doesn't happen though if the device is already plugged to the hub > > before attaching the

Re: [RFC v2 1/5] UDC: Split the driver into amd (pci) and Synopsys core driver

On 01/17/2017 12:05 AM, Raviteja Garimella wrote: > This patch splits the amd5536udc driver into two -- one that does > pci device registration and the other file that does the rest of > the driver tasks like the gadget/ep ops etc for Synopsys UDC. > > This way of splitting helps in exporting

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

* Bin Liu [170118 10:43]: > On Wed, Jan 18, 2017 at 08:53:09AM -0800, Tony Lindgren wrote: > > Hi, > > > > * Bin Liu [170118 06:26]: > > > With this v3, I still get -71 error when a device is plugged to a hub to > > > musb. It doesn't happen though if the device is

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

* Tony Lindgren [170118 10:15]: > * Grygorii Strashko [170118 10:05]: > > > > > > On 01/18/2017 10:53 AM, Tony Lindgren wrote: > > > Hi, > > > > > > * Bin Liu [170118 06:26]: > > >> With this v3, I still get -71 error when a device is

Re: Strange behaviour of U2F usb key

Hi Greg, Sorry for the long delay before this message. Real life intruded on my computing time. On 05/01/17 12:51, Greg KH wrote: > Are you sure the device even works properly? It could be the device has > problems returning data correctly. Can you run usbmon to see if the > data is being

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

On 01/18/2017 10:53 AM, Tony Lindgren wrote: > Hi, > > * Bin Liu [170118 06:26]: >> With this v3, I still get -71 error when a device is plugged to a hub to >> musb. It doesn't happen though if the device is already plugged to the hub >> before attaching the hub to musb. >> >> [

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

Hi, * Bin Liu [170118 06:26]: > With this v3, I still get -71 error when a device is plugged to a hub to > musb. It doesn't happen though if the device is already plugged to the hub > before attaching the hub to musb. > > [ 177.579300] usb 1-1: reset high-speed USB device number

[BISSECTED]: BUG: usb: dwc3: usb ports not working anymore on odroid-XU4

Hi, Since commit c499ff71ff2a2 ("usb: dwc3: core: re-factor init and exit paths") (merged in 4.8), the usb ports on odroid-XU4 don't work anymore. [ Actually, it's commit 2164a476205ccc ("usb: dwc3: set SUSPHY bit for all cores"), cf below ] Inserting an usb key (USB2.0) on the USB3.0 port

Re: [PATCHv3] dmaengine: cppi41: Fix oops in cppi41_runtime_resume

On Tue, Jan 17, 2017 at 09:55:24AM -0800, Tony Lindgren wrote: > Commit fdea2d09b997 ("dmaengine: cppi41: Add basic PM runtime support") > together with recent MUSB changes allowed USB and DMA on BeagleBone to idle > when no cable is connected. But looks like few corner case issues still > remain.

[RFC PATCH 2/3] usb: phy: msm: Remove the set_power callback

Since it will not set the PMIC current drawn from USB configuration by set_power callback, then remove it. Signed-off-by: Baolin Wang --- drivers/usb/phy/phy-msm-usb.c | 18 -- 1 file changed, 18 deletions(-) diff --git a/drivers/usb/phy/phy-msm-usb.c

[RFC PATCH 0/3] Remove some dummy set_power callbacks

In future we plan to introduce USB charger to set PMIC current drawn from USB configuration, instead of using set_power callback in phy driver. Moreover in these 3 phy drivers, the set_power callback did not implement anything to set PMIC current, thus we should remove them. Baolin Wang (3):

[RFC PATCH 1/3] usb: phy: ab8500: Remove the set_power callback

There are no users will use the vbus_draw variable set by set_power() callback to set the vbus current. Thus we can remove it. Signed-off-by: Baolin Wang --- drivers/usb/phy/phy-ab8500-usb.c | 20 1 file changed, 20 deletions(-) diff --git

[RFC PATCH 3/3] usb: phy: fsl: Remove the set_power callback

Since the set_power callback did not do anything for power setting, then remove it. Signed-off-by: Baolin Wang --- drivers/usb/phy/phy-fsl-usb.c | 12 1 file changed, 12 deletions(-) diff --git a/drivers/usb/phy/phy-fsl-usb.c

Re: [PATCH v5 4/6] usb: xhci: use bus->sysdev for DMA configuration

On 12.01.2017 10:38, Roger Quadros wrote: Mathias, On 11/01/17 17:08, Alan Stern wrote: On Wed, 11 Jan 2017, Mathias Nyman wrote: On 17.11.2016 13:43, Sriram Dash wrote: From: Arnd Bergmann For xhci-hcd platform device, all the DMA parameters are not configured properly,

Darlehen Angebot

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 weitere

Geschäftsvorschlag

Lieber Freund. Erlauben Sie mir, auf diese Weise auf Sie zuzugehen. Ich bin Dr. Arnold Kristofferson, ein US-Auftragnehmer, der mit Nichtkämpfer US Marine in Ba'qubah, Irak arbeitet. Ich habe die Summe von 10,6 Millionen Dollar, die ich aus einem Rohöl-Deal gemacht habe, und ich möchte, dass

[PATCH v4 3/3] USB3/DWC3: Enable undefined length INCR burst type

Enable the undefined length INCR burst type and set INCRx. Different platform may has the different burst size type. In order to get best performance, we need to tune the burst size to one special value, instead of the default value. Signed-off-by: Changming Huang

[PATCH v4 1/3] USB3/DWC3: Add definition for global soc bus configuration register

Add the macro definition for global soc bus configuration register 0/1 Signed-off-by: Changming Huang --- Changes in v4: - no change Changes in v3: - no change Changes in v2: - split the patch - add more macro definition for soc bus configuration register

[PATCH v4 2/3] USB3/DWC3: Add property "snps,incr-burst-type-adjustment" for INCR burst type

Property "snps,incr-burst-type-adjustment = , ..." for USB3.0 DWC3. When Just one value means INCRx mode with fix burst type. When more than one value, means undefined length burst mode, USB controller can use the length less than or equal to the largest enabled burst length. While enabling