Re: Sabrent USB 3.0 to SSD // "UAS is blacklisted for this device, using usb-storage instead"

2018-10-22 Thread Julian Xhokaxhiu
Hi Oliver, thank you very much for the reply. I'll stay tuned. Feel free to approach me if needed. Best regards, Julian Xhokaxhiu Full Stack Developer, IT Practised (ISCED 4) https://julianxhokaxhiu.com/ On Mon, Oct 22, 2018 at 10:39 AM Oliver Neukum wrote: > > On Sa, 2018-10-20 at 14:34 +0200

Re: Query on usb/core/devio.c

2018-10-22 Thread Alan Stern
On Mon, 22 Oct 2018, Oliver Neukum wrote: > On Do, 2018-10-18 at 13:42 -0400, Alan Stern wrote: > > On Thu, 18 Oct 2018, Mayuresh Kulkarni wrote: > > > > > > The only way to make the ioctl work properly is to have it do a > > > > runtime-PM put at the start and then a runtime-PM get before it >

Re: [PATCH v2 4/4] doc: usb: ci-hdrc-usb2: Add pinctrl properties for HSIC pin groups

2018-10-22 Thread Fabio Estevam
On Mon, Oct 22, 2018 at 11:55 AM Schrempf Frieder wrote: > I think you forgot to improve this description. Maybe something like this: > > pinctrl-names: Names for optional pin modes for "default", "host" or > "device". In case of HSIC-mode "idle" and "active" pin >

Re: [PATCH v2 4/4] doc: usb: ci-hdrc-usb2: Add pinctrl properties for HSIC pin groups

2018-10-22 Thread Schrempf Frieder
On 22.10.18 07:43, Peter Chen wrote: > For USB HSIC, the data and strobe pin needs to be pulled down > at default, we consider it as "idle" state. When the USB host > is ready to be used, the strobe pin needs to be pulled up, > we consider it as "active" state. > > Signed-off-by: Peter Chen > ---

RE: [PATCH v2 4/4] doc: usb: ci-hdrc-usb2: Add pinctrl properties for HSIC pin groups

2018-10-22 Thread Peter Chen
> On Mon, Oct 22, 2018 at 11:55 AM Schrempf Frieder > wrote: > > > I think you forgot to improve this description. Maybe something like this: > > > > pinctrl-names: Names for optional pin modes for "default", "host" or > > "device". In case of HSIC-mode "idle" and "active" pin >

Re: [PATCH v2 0/4] usb: chipidea: imx: add HSIC support

2018-10-22 Thread Schrempf Frieder
Hi Peter, On 22.10.18 07:42, Peter Chen wrote: > Most of NXP (Freescale) i.mx USB part has HSIC support, in this series, > we add support for them, it should cover all imx6 and imx7d SoC. > > Changes for v2: > - Compile error reported by kbuild robot [Patch 2/4] > - Comment from Frieder Schrempf

RE: [PATCH v2 0/4] usb: chipidea: imx: add HSIC support

2018-10-22 Thread Peter Chen
> As I already posted when I was testing v1 last week, there is a problem with > auto > suspend with my LAN9730 chip. I thought it was a problem with the > smsc95xx/usbnet driver, but I'm not so sure anymore. > > So I'd like to figure out if it has something to do with the HSIC patches. I > ho

RE: SMSC9730 Autosuspend/Resume Questions

2018-10-22 Thread Nisar.Sayed
Hi Frieder, > Hi, > > I recently tested a board with SMSC9730 connected via USB HSIC to an > i.MX6S SOC. I used these patches on top of v4.14-rc8 for the USB HSIC > support: [1]. > > When I turned on autosuspend, the smsc95xx stopped in the middle of the > suspending routine and /sys/bus/usb/dev

Re: SMSC9730 Autosuspend/Resume Questions

2018-10-22 Thread Frieder Schrempf
Hi Nisar, On 22.10.18 09:03, nisar.sa...@microchip.com wrote: Hi Frieder, Hi, I recently tested a board with SMSC9730 connected via USB HSIC to an i.MX6S SOC. I used these patches on top of v4.14-rc8 for the USB HSIC support: [1]. When I turned on autosuspend, the smsc95xx stopped in the mid

Re: [PATCH 1/2] usb: xhci: fix uninitialized completion when USB3 port got wrong status

2018-10-22 Thread Mathias Nyman
On 21.10.2018 20:08, Aaron Ma wrote: Realtek USB3.0 Card Reader [0bda:0328] reports wrong port status on Cannon lake PCH USB3.1 xHCI [8086:a36d] after resume from S3, after clear port reset it works fine. Since this device is registered on USB3 roothub at boot, when port status reports not super

Re: [PATCH 1/2] usb: xhci: fix uninitialized completion when USB3 port got wrong status

2018-10-22 Thread Aaron Ma
On 10/22/18 9:12 PM, Mathias Nyman wrote: > On 21.10.2018 20:08, Aaron Ma wrote: >> Realtek USB3.0 Card Reader [0bda:0328] reports wrong port status on >> Cannon lake PCH USB3.1 xHCI [8086:a36d] after resume from S3, >> after clear port reset it works fine. >> >> Since this device is registered

[PATCH v2 1/2] usb: xhci: fix uninitialized completion when USB3 port got wrong status

2018-10-22 Thread Aaron Ma
Realtek USB3.0 Card Reader [0bda:0328] reports wrong port status on Cannon lake PCH USB3.1 xHCI [8086:a36d] after resume from S3, after clear port reset it works fine. Since this device is registered on USB3 roothub at boot, when port status reports not superspeed, xhci_get_port_status will call a

[PATCH v2 2/2] usb: xhci: fix timeout for transition from RExit to U0

2018-10-22 Thread Aaron Ma
This definition is used by msecs_to_jiffies in milliseconds. According to the comments, max rexit timeout should be 20ms. Align with the comments to properly calculate the delay. Verified on Sunrise Point-LP and Cannon Lake. Cc: sta...@vger.kernel.org Signed-off-by: Aaron Ma --- drivers/usb/hos

Re: [PATCH 1/2] usb: xhci: fix uninitialized completion when USB3 port got wrong status

2018-10-22 Thread Aaron Ma
On 10/22/18 9:12 PM, Mathias Nyman wrote: > On 21.10.2018 20:08, Aaron Ma wrote: >> Realtek USB3.0 Card Reader [0bda:0328] reports wrong port status on >> Cannon lake PCH USB3.1 xHCI [8086:a36d] after resume from S3, >> after clear port reset it works fine. >> >> Since this device is registered