Re: [PATCH] usb: move usb_calc_bus_time into common code

On 2/19/2016 2:48 PM, Doug Anderson wrote: > Hi, > > On Fri, Feb 19, 2016 at 1:52 PM, Alan Stern wrote: >> On Fri, 19 Feb 2016, Arnd Bergmann wrote: >> >>> The dwc2 dual-role USB controller driver has started calling >>> usb_calc_bus_time, and does so regardless of

[PATCH] usb: dwc3: Validate the maximum_speed parameter

Check that dwc->maximum_speed is set to a valid value. Also add an error when we use it later if we encounter an invalid value. Signed-off-by: John Youn --- Hi Felipe, This patch depends on the previous SuperSpeed patches I sent. Let me know if you'd rather I amend the

Re: [PATCH] usb: move usb_calc_bus_time into common code

Hi, On Fri, Feb 19, 2016 at 1:52 PM, Alan Stern wrote: > On Fri, 19 Feb 2016, Arnd Bergmann wrote: > >> The dwc2 dual-role USB controller driver has started calling >> usb_calc_bus_time, and does so regardless of whether it is >> being built as a host controller or

Re: "reset full-speed USB device number 6 using ehci-pci" with Dell Inspiron 15R 5537

On Fri, 19 Feb 2016, Daniel Fraga wrote: > On Fri, 19 Feb 2016 14:13:25 -0500 (EST) > Alan Stern wrote: > > > -22 is -EINVAL, so we need to figure out which of the many possible > > EINVAL errors you're getting. Try the patch below. > > I applied your patch,

Re: [PATCH] usb: move usb_calc_bus_time into common code

On Fri, 19 Feb 2016, Arnd Bergmann wrote: > The dwc2 dual-role USB controller driver has started calling > usb_calc_bus_time, and does so regardless of whether it is > being built as a host controller or gadget. In case all Out of curiosity... Why does dwc2 need to calculate bus times when it

[PATCH] usb: move usb_calc_bus_time into common code

The dwc2 dual-role USB controller driver has started calling usb_calc_bus_time, and does so regardless of whether it is being built as a host controller or gadget. In case all USB host support is disabled (CONFIG_USB=n), this now causes a link error: ERROR: "usb_calc_bus_time"

Re: [PATCH] Support HP lt4114 LTE Module (Huawei ME206V-561)

On Fri, Feb 19, 2016 at 2:31 AM, Bjørn Mork wrote: > Good. So you have a few alternative configs here. I forgot to ask, but > I assume you've ended up with cfg #2 by default (because Linux has a > class preference, making it select the first config with a non 0xff > class as the

Re: driver migration

Greg KH writes: > > On Fri, Feb 19, 2016 at 06:49:50AM +, tilman wrote: > > Hello > > > > I configured and setup a more recent kernel: V4.5.0-rc4 > > > > The driver compiles and inserts. > > What driver? You have provided no context here :( My apologies -- what I meant to

Re: "reset full-speed USB device number 6 using ehci-pci" with Dell Inspiron 15R 5537

On Fri, 19 Feb 2016 14:13:25 -0500 (EST) Alan Stern wrote: > -22 is -EINVAL, so we need to figure out which of the many possible > EINVAL errors you're getting. Try the patch below. I applied your patch, but when it wakes up from S3, the system is stalled:

Re: [PATCH] Support HP lt4114 LTE Module (Huawei ME206V-561)

On Fri, 2016-02-19 at 18:21 +0100, Bjørn Mork wrote: > Dan Williams writes: > > On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote: > > > > > cfg #1 > > > MI_00 HP Mobile Connect - PC UI Interface > > > MI_01 HP Mobile Connect - Application Interface > > > MI_02 HP Mobile

[GIT PULL] USB-serial fixes for v4.5-rc5

Hi Greg, Here are some new device ids for rc5. Thanks, Johan The following changes since commit 18558cae0272f8fd9647e69d3fec1565a7949865: Linux 4.5-rc4 (2016-02-14 13:05:20 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git

Re: "reset full-speed USB device number 6 using ehci-pci" with Dell Inspiron 15R 5537

On Thu, 18 Feb 2016, Daniel Fraga wrote: > On Thu, 18 Feb 2016 15:23:00 -0500 (EST) > Alan Stern wrote: > > > Something like the patch below (untested). > > > + dev_info(>dev, "post reset hid_start_in -> %d\n", status); > > Ok, so I got the following: > >

Re: [PATCH v4 1/2] usb: musb: Fix DMA for host mode

Hello. On 02/19/2016 07:41 PM, Joshua Henderson wrote: From: Cristian Birsan Commit ac33cdb16681 ("usb: musb: Remove ifdefs for musb_host_rx in musb_host.c part5") introduces a problem setting DMA host mode. This commit fixes the done condition that advances

Re: [PATCH] Support HP lt4114 LTE Module (Huawei ME206V-561)

Dan Williams writes: > On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote: > >> cfg #1 >> MI_00 HP Mobile Connect - PC UI Interface >> MI_01 HP Mobile Connect - Application Interface >> MI_02 HP Mobile Connect - Modem >> MI_03 HP Mobile Connect - Network Card (jungo ncm) >>

Re: driver migration

On Fri, Feb 19, 2016 at 06:49:50AM +, tilman wrote: > Hello > > I configured and setup a more recent kernel: V4.5.0-rc4 > > The driver compiles and inserts. What driver? You have provided no context here :( > When I plugin the USB-Dongle, the machine > freezes (not sure whether it

[PATCH v4 2/2] usb: musb: Fix DMA desired mode for Mentor DMA engine

From: Cristian Birsan Commit 754fe4a92c07 ("usb: musb: Remove ifdefs for TX DMA for musb_host.c") introduces a problem setting the desired channel mode for the Mentor DMA engine. There is a case where an address is incorrectly assigned to the DMA channel desired

Re: [PATCH 2/5] usb: musb: core: added helper functions for parsing DT

Hi, On Fri, Feb 12, 2016 at 03:58:40PM +0100, Petr Kulhavy wrote: > This adds two functions to get DT properties "mentor,power" and "dr_mode": > musb_get_power() and musb_mode musb_get_mode() Please add revision # in the [PATCH...] prefix in subject. > > Signed-off-by: Petr Kulhavy

[PATCH v4 1/2] usb: musb: Fix DMA for host mode

From: Cristian Birsan Commit ac33cdb16681 ("usb: musb: Remove ifdefs for musb_host_rx in musb_host.c part5") introduces a problem setting DMA host mode. This commit fixes the done condition that advances the musb schedule. Without this patch the the

Re: [PATCH] Support HP lt4114 LTE Module (Huawei ME206V-561)

On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote: > On 2016-02-19 17:31, Bjørn Mork wrote: > > Daniel Johnson writes: > > > > > > > Currently 4 ttyUSB devices are detected, but only the second > > > > > two respond to > > > > > AT commands. The first two serial ports may

[PATCH] usb: musb: host: Fix NULL pointer dereference in SMP environment

In multi-core SoC, if enable USB endpoint/transmit urb/disable USB endpoint repeatedly,it can cause a NULL pointer dereference bug: Unable to handle kernel NULL pointer dereference at virtual address 0010 pgd = d3eb4000 [0010] *pgd= Internal error: Oops: 5 [#1] PREEMPT SMP Pid:

Re: [PATCH 2/5] usb: musb: core: added helper functions for parsing DT

Hi, On Fri, Feb 19, 2016 at 02:08:37PM +0200, Felipe Balbi wrote: > > Hi, > > Sergei Shtylyov writes: > > On 2/19/2016 10:23 AM, Felipe Balbi wrote: > > > >>> This adds two functions to get DT properties "mentor,power" and > >>> "dr_mode": > >>>

[HELP] USB 3.0 PCI Endpoint problem

Hi to all! I am testing a PCIe Root Complex prototyping setup in which I have a USB 3.0 host as a PCI Endpoint. Running in an ARC CPU platform it works well, but when running in an emulated ARM64 (this is done by a Synopsys virtualization tool) the endpoint initialization fails as can be seen in

RE: [RESEND PATCH v6 07/10] usb: chipidea: otg: enable HNP polling support for gadget and host

Hi, > -Original Message- > From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb- > ow...@vger.kernel.org] On Behalf Of Jun Li > Sent: Friday, February 19, 2016 10:49 PM > To: Felipe Balbi ; ba...@kernel.org; Peter Chen > > Cc:

Re: [PATCH RESEND] usb: phy: mxs: Suggest passing "usbcore.autosuspend=-1" for mx23/mx28

On Fri, Feb 19, 2016 at 12:13 PM, Felipe Balbi wrote: > h, okay. So you have another problem, actually. Seems like ci_hdrc > just shouldn't call your phy->suspend(), or your phy->suspend() > shouldn't do anything. How about below? > > @@ -370,6 +370,9 @@ static int

RE: [RESEND PATCH v6 07/10] usb: chipidea: otg: enable HNP polling support for gadget and host

Hi Felipe, > -Original Message- > From: Felipe Balbi [mailto:bal...@gmail.com] > Sent: Friday, February 19, 2016 10:07 PM > To: Jun Li ; ba...@kernel.org; Peter Chen > > Cc: linux-usb@vger.kernel.org; Jun Li > Subject: Re: [RESEND

USB oops regression caused by -stable patch

This upstream commit is causing an oops: d8f00cd685f5 ("usb: hub: do not clear BOS field during reset device") This patch has already been included in several -stable kernels. Here are the affected kernels: 4.5.0-rc4 (current git) 4.4.2 4.3.6 (currently in review) 4.1.18 3.18.27 3.14.61 How to

Re: [PATCH] Support HP lt4114 LTE Module (Huawei ME206V-561)

On 2016-02-19 17:31, Bjørn Mork wrote: Daniel Johnson writes: Currently 4 ttyUSB devices are detected, but only the second two respond to AT commands. The first two serial ports may be falsely detected. One of them is likely a QCDM port if this is really a Qualcomm based

Re: [PATCH RESEND] usb: phy: mxs: Suggest passing "usbcore.autosuspend=-1" for mx23/mx28

Hi, Fabio Estevam writes: > On Fri, Feb 19, 2016 at 11:33 AM, Felipe Balbi wrote: > >> alright, in which sense doesn't it help ? Which platform did you use ? > > USB devices are not recognized with your patch applied on a mx28 board > with an on-board USB

Re: [RESEND PATCH v6 07/10] usb: chipidea: otg: enable HNP polling support for gadget and host

hi, Li Jun writes: > Enable HNP polling support for chipidea gadget and allocate memory > for host request flag when otg fsm init. > > Acked-by: Peter Chen > Signed-off-by: Li Jun Why do you guys do this to me ? It's v6 and this thing still

Re: [PATCH RESEND] usb: phy: mxs: Suggest passing "usbcore.autosuspend=-1" for mx23/mx28

On Fri, Feb 19, 2016 at 11:33 AM, Felipe Balbi wrote: > alright, in which sense doesn't it help ? Which platform did you use ? USB devices are not recognized with your patch applied on a mx28 board with an on-board USB hub and if I remove 'usbcore.autosuspend=-1' from the

RE: [PATCH v6 00/10] add HNP polling support for usb otg fsm

Hi Felipe, > -Original Message- > From: Felipe Balbi [mailto:bal...@gmail.com] > Sent: Friday, February 19, 2016 4:58 PM > To: Jun Li ; Felipe Balbi > Cc: linux-usb@vger.kernel.org; Peter Chen ; > hzpeterc...@gmail.com;

Re: [PATCH RESEND] usb: phy: mxs: Suggest passing "usbcore.autosuspend=-1" for mx23/mx28

Hi, Fabio Estevam writes: > Hi Felipe, > > On Fri, Feb 19, 2016 at 10:05 AM, Felipe Balbi wrote: > >> how about detecting that you're running on mx23/mx28 and returning >> -EBUSY on your runtime_idle implementation ? You already have the basics >> done for

Re: [PATCH RESEND] usb: phy: mxs: Suggest passing "usbcore.autosuspend=-1" for mx23/mx28

Hi Felipe, On Fri, Feb 19, 2016 at 10:05 AM, Felipe Balbi wrote: > how about detecting that you're running on mx23/mx28 and returning > -EBUSY on your runtime_idle implementation ? You already have the basics > done for it. Care to test below and tell me whether it helps ?

Re: [PATCH 2/5] usb: musb: core: added helper functions for parsing DT

Hi, Sergei Shtylyov writes: > On 2/19/2016 10:23 AM, Felipe Balbi wrote: > >>> This adds two functions to get DT properties "mentor,power" and >>> "dr_mode": >>> musb_get_power() and musb_mode musb_get_mode() >>> >>> Signed-off-by: Petr

Re: [PATCH RESEND] usb: phy: mxs: Suggest passing "usbcore.autosuspend=-1" for mx23/mx28

Hi, Fabio Estevam writes: > From: Fabio Estevam > > On a mx28 board with a USB hub the following error is observed: > > hub 1-1:1.0: USB hub found > hub 1-1:1.0: 2 ports detected > usb 1-1: USB disconnect, device number 2 > usb usb1-port1: cannot

[PATCH RESEND] usb: phy: mxs: Suggest passing "usbcore.autosuspend=-1" for mx23/mx28

From: Fabio Estevam On a mx28 board with a USB hub the following error is observed: hub 1-1:1.0: USB hub found hub 1-1:1.0: 2 ports detected usb 1-1: USB disconnect, device number 2 usb usb1-port1: cannot reset (err = -32) usb usb1-port1: cannot reset (err = -32) usb

Re: [PATCH 2/5] usb: musb: core: added helper functions for parsing DT

On 2/19/2016 10:23 AM, Felipe Balbi wrote: This adds two functions to get DT properties "mentor,power" and "dr_mode": musb_get_power() and musb_mode musb_get_mode() Signed-off-by: Petr Kulhavy seems like I don't have patch 1/5. After fixing Sergei's comments, please resend

ftdi_sio: ftdi_set_termios

Dear Bill and all, I am facing an issue with ftdi_sio module and FTDI FT232-based devices. Now I am trying to understand where the origin is. By indirect evidences, I think that there is a small time gap between return of tcsetattr(fd_, TCSANOW, _termios) and actual settings application in the

Re: [PATCH] Support HP lt4114 LTE Module (Huawei ME206V-561)

Daniel Johnson writes: >>> Currently 4 ttyUSB devices are detected, but only the second two respond to >>> AT commands. The first two serial ports may be falsely detected. >> >> One of them is likely a QCDM port if this is really a Qualcomm based >> device. The other might

Re: [PATCH v6 1/1] USB: core: let USB device know device node

On Friday 19 February 2016 17:26:15 Peter Chen wrote: > From: Peter Chen > > Although most of USB devices are hot-plug's, there are still some devices > are hard wired on the board, eg, for HSIC and SSIC interface USB devices. > If these kinds of USB devices are

[PATCH v6 1/1] USB: core: let USB device know device node

From: Peter Chen Although most of USB devices are hot-plug's, there are still some devices are hard wired on the board, eg, for HSIC and SSIC interface USB devices. If these kinds of USB devices are multiple functions, and they can supply other interfaces like i2c,

[PATCH] MAINTAINERS: drop OMAP USB and MUSB maintainership

Now that I have switched to another company, I won't be able to help by maintaining OMAP USB Support and/or the MUSB driver. OMAP USB Support is left Orphaned. MUSB's new maintainer will be Bin Liu from Texas Instruments who has accepted to take over starting with v4.6. Cc: Bin Liu

RE: [PATCH v6 00/10] add HNP polling support for usb otg fsm

hi, Jun Li writes: > Hi Felipe > > I didn't get any response for this request, if you need a resend > of the whole patchset, please let me know. please do, I can't find these on my inbox :-s sorry. With all the changes lately, it took me a while to get things properly setup

Re: [PATCH] Support HP lt4114 LTE Module (Huawei ME206V-561)

>> Currently 4 ttyUSB devices are detected, but only the second two respond to >> AT commands. The first two serial ports may be falsely detected. > > One of them is likely a QCDM port if this is really a Qualcomm based > device. The other might be an inactive NMEA port. Serial doesn't >

Re: [PATCH v5 1/1] USB: core: let USB device know device node

Hi Peter, Am Dienstag, den 16.02.2016, 16:42 +0800 schrieb Peter Chen: > From: Peter Chen > > Although most of USB devices are hot-plug's, there are still some devices > are hard wired on the board, eg, for HSIC and SSIC interface USB devices. > If these kinds of USB

Re: [PATCH] Support HP lt4114 LTE Module (Huawei ME206V-561)

Daniel Patrick Johnson writes: > Adds HP lt4114 LTE module USB ID as a Huawei device. > > Currently 4 ttyUSB devices are detected, but only the second two respond to > AT commands. The first two serial ports may be falsely detected. One of them is likely a QCDM port if this

[PATCH] Support HP lt4114 LTE Module (Huawei ME206V-561)

Adds HP lt4114 LTE module USB ID as a Huawei device. Currently 4 ttyUSB devices are detected, but only the second two respond to AT commands. The first two serial ports may be falsely detected. Of the two responsive serial devices the first is the source of unsolicited information such as a SIM