Re: [Patch V3 4/8] dt-bindings: usb: Add NVIDIA Tegra XUSB device mode controller binding

2019-06-17 Thread Nagarjuna Kristam
On 14-06-2019 03:02, Rob Herring wrote: > On Thu, May 16, 2019 at 12:09:28PM +0530, Nagarjuna Kristam wrote: >> Add device-tree binding documentation for the XUSB device mode controller >> present on Tegra210 SoC. This controller supports the USB 3.0 >> specification. >> >> Signed-off-by: Nagarj

Re: [PATCH] usb: Replace a < b ? a : b construct with min_t(type, a, b) in drivers/usb

2019-06-17 Thread Greg KH
On Mon, Jun 17, 2019 at 04:30:50PM -0700, d...@turingmachine.org wrote: > From: Daniel M German > > Use min_t to find the minimum of two values instead of using the ?: operator. Why is min_t() needed for all of these and not just min()? > > This change does not alter functionality. It is merel

Re: [PATCH 8/8] xhci: tegra: enable ELPG for runtime/system PM

2019-06-17 Thread Greg KH
On Fri, Jun 14, 2019 at 03:48:24PM +0800, JC Kuo wrote: > This commit enables XUSB host controller ELPG for runtime and system > power management. > > NEED CLEANUP. Odd kernel changelog comment... Please cleanup when you resend. :) thanks, greg k-h

[PATCH] usb: Replace a < b ? a : b construct with min_t(type, a, b) in drivers/usb

2019-06-17 Thread dmg
From: Daniel M German Use min_t to find the minimum of two values instead of using the ?: operator. This change does not alter functionality. It is merely cosmetic intended to improve the readability of the code. Signed-off-by: Daniel M German --- drivers/usb/gadget/function/u_ether.c | 2 +-

RE: [RFC] Sorting out dwc3 ISOC endpoints once and for all

2019-06-17 Thread John Youn
> -Original Message- > From: Thinh Nguyen > Sent: Monday, June 17, 2019 12:09 PM > To: John Youn ; Felipe Balbi > ; John Youn > Cc: linux-usb@vger.kernel.org > Subject: Re: [RFC] Sorting out dwc3 ISOC endpoints once and for all > > Hi, > > John Youn wrote: > >> -Original Message--

Re: [PATCH] usb: gadget: avoid using gadget after freed

2019-06-17 Thread Lianwei Wang
On Mon, Jun 17, 2019 at 5:40 AM Felipe Balbi wrote: > > Lianwei Wang writes: > > > The udc and gadget device will be deleted when udc device is > > disconnected and the related function will be unbind with it. > > > > But if the configfs is not deleted, then the function object > > will be kept a

Re: [RFC] Sorting out dwc3 ISOC endpoints once and for all

2019-06-17 Thread Thinh Nguyen
Hi, John Youn wrote: >> -Original Message- >> From: Felipe Balbi >> Sent: Friday, June 7, 2019 2:50 AM >> To: John Youn >> Cc: linux-usb@vger.kernel.org >> Subject: [RFC] Sorting out dwc3 ISOC endpoints once and for all >> > ++ Thinh > > Hi Felipe, > > Sorry, missed this e-mail. > >> Now

RE: [RFC] Sorting out dwc3 ISOC endpoints once and for all

2019-06-17 Thread John Youn
> -Original Message- > From: Felipe Balbi > Sent: Friday, June 7, 2019 2:50 AM > To: John Youn > Cc: linux-usb@vger.kernel.org > Subject: [RFC] Sorting out dwc3 ISOC endpoints once and for all > ++ Thinh Hi Felipe, Sorry, missed this e-mail. > Now that we have dwc3_gadget_start_is

Re: Slow I/O on USB media

2019-06-17 Thread Alan Stern
On Mon, 17 Jun 2019, Andrea Vai wrote: > Il giorno lun, 17/06/2019 alle 12.14 -0400, Alan Stern ha scritto: > > On Mon, 17 Jun 2019, Andrea Vai wrote: > > > > > [...] > > > > > > That happened ALL times, so I never encountered a kernel that made > > me > > > say "git bisect good". > > > > Reall

Re: Slow I/O on USB media

2019-06-17 Thread Andrea Vai
Il giorno lun, 17/06/2019 alle 12.14 -0400, Alan Stern ha scritto: > On Mon, 17 Jun 2019, Andrea Vai wrote: > > > [...] > > > > That happened ALL times, so I never encountered a kernel that made > me > > say "git bisect good". > > Really? That strongly suggests that the 4.20 kernel also should

Re: Slow I/O on USB media

2019-06-17 Thread Alan Stern
On Mon, 17 Jun 2019, Andrea Vai wrote: > Il giorno lun, 10/06/2019 alle 10.40 -0400, Alan Stern ha scritto: > > On Sat, 8 Jun 2019, Andrea Vai wrote: > > > > [...] > > Hi, > I have concluded the (third) bisect, and still haven't come to an > end, but I have collected as much information as I c

Re: [PATCH v4 6/8] ARM: dts: imx7ulp: add imx7ulp USBOTG1 support

2019-06-17 Thread Sergei Shtylyov
Hello! On 06/17/2019 04:13 AM, Peter Chen wrote: [...] >>> Signed-off-by: Peter Chen >>> --- >>> arch/arm/boot/dts/imx7ulp.dtsi | 28 >>> 1 file changed, 28 insertions(+) >>> >>> diff --git a/arch/arm/boot/dts/imx7ulp.dtsi >>> b/arch/arm/boot/dts/imx7ulp.dtsi inde

Re: [PATCH] usb: core: devio: add ioctls for suspend and resume

2019-06-17 Thread Alan Stern
On Mon, 17 Jun 2019, Mayuresh Kulkarni wrote: > > (Note: I imagine you might run into trouble because devices generally  > > do not get put into runtime suspend immediately.  So if you call the  > > USBDEVFS_SUSPEND ioctl and then the USBDEVFS_WAIT_FOR_RESUME ioctl, > > the  > > wait will return i

Re: Slow I/O on USB media

2019-06-17 Thread Andrea Vai
Il giorno lun, 10/06/2019 alle 10.40 -0400, Alan Stern ha scritto: > On Sat, 8 Jun 2019, Andrea Vai wrote: > > [...] Hi, I have concluded the (third) bisect, and still haven't come to an end, but I have collected as much information as I can: - I started again from: cd /NoBackup/kernel rm -rf

Re: [PATCH] usb: gadget: avoid using gadget after freed

2019-06-17 Thread Felipe Balbi
Lianwei Wang writes: > The udc and gadget device will be deleted when udc device is > disconnected and the related function will be unbind with it. > > But if the configfs is not deleted, then the function object > will be kept and the bound status is kept true. > > Then after udc device is conne

Force Feedback support not recognized on Granite Devices Simucube

2019-06-17 Thread Bernd Steinhauser
Resending this message to linux input as suggested. Hi, I own a Granite Devices Simucube force feedback wheel which I'd like to get working under Linux. The current status is that if I use a tool to check/test the FFB, it tells me that the device does not support FFB. I'm also using the device

Re: [PATCH] usb: core: devio: add ioctls for suspend and resume

2019-06-17 Thread Mayuresh Kulkarni
On Wed, 2019-06-05 at 17:02 -0400, Alan Stern wrote: > On Wed, 5 Jun 2019, Greg KH wrote: > > > > > On Fri, May 10, 2019 at 11:01:09AM +0100, Mayuresh Kulkarni wrote: > > > > > > - The current driver increments the PM ref-count in its .open > > > API and decrements it in its .close API. > > > -

Re: Force Feedback support not recognized on Granite Devices Simucube

2019-06-17 Thread Bernd Steinhauser
On 17/06/19 12:57, Oliver Neukum wrote: Am Montag, den 17.06.2019, 12:35 +0200 schrieb Bernd Steinhauser: The device advertises as MCS, Granite Devices SimuCUBE with id 16d0:0d5a, I'll attach lsusb output. Upon connection, the device is recognized and the output is: [ 3271.812807] usb 1-2.4.2:

Re: Force Feedback support not recognized on Granite Devices Simucube

2019-06-17 Thread Oliver Neukum
Am Montag, den 17.06.2019, 12:35 +0200 schrieb Bernd Steinhauser: > > The device advertises as MCS, Granite Devices SimuCUBE with id 16d0:0d5a, > I'll attach lsusb output. > Upon connection, the device is recognized and the output is: > > [ 3271.812807] usb 1-2.4.2: new full-speed USB device num

Force Feedback support not recognized on Granite Devices Simucube

2019-06-17 Thread Bernd Steinhauser
Hi, I own a Granite Devices Simucube force feedback wheel which I'd like to get working under Linux. The current status is that if I use a tool to check/test the FFB, it tells me that the device does not support FFB. I'm also using the device under Windows 7 and there it works without any spec

Re: DWC3 USB hub issue

2019-06-17 Thread Roger Quadros
On 17/06/2019 10:13, Felipe Balbi wrote: > > Hi, > > Manivannan Sadhasivam writes: >> Hello, >> >> I'm trying to upstream Designware USB3 host driver present in the Actions >> Semi S900 SoC. It can successfully detect the USB hub but when any of the >> USB device got plugged in, it fails with

Re: DWC3 USB hub issue

2019-06-17 Thread Felipe Balbi
Hi, Manivannan Sadhasivam writes: > Hello, > > I'm trying to upstream Designware USB3 host driver present in the Actions > Semi S900 SoC. It can successfully detect the USB hub but when any of the > USB device got plugged in, it fails with following error: > > [4.365566] usb usb1-port1: conn