Re: uas failing on multiple disk access on a jmicron JMS567 bridge

Hi Christoph, Out of curiosity, what exact device is this? I have an multi-disk JMS567 based enclosure which reports the same IDs from lsusb, doesn't work with uas at all. According to the datasheet for JMS567 it should support UAS, but I've received conflicting information from the manufacturer

Re: [PATCH v2] usb: typec: Add a sysfs node to manage port type

Thanks comments inline. On Tue, May 23, 2017 at 7:38 PM, Guenter Roeck wrote: > On 05/23/2017 06:28 PM, Badhri Jagan Sridharan wrote: >> >> User space applications in some cases have the need to enforce a >> specific port type(DFP/UFP/DRP). This change allows userspace to >>

Re: USB hub clear POWER feature -> device still in 'lsusb' ?!

Hi Greg, On Wed, May 24, 2017 at 09:19:14AM +0200, Greg KH wrote: > > * In absence of any sysfs control or other API exposed to userland, I'm > > using uhubctl (https://github.com/mvp/uhubctl) to directly clear the > > POWER feature on said downstream USB port of the hub. > > > > * The Linux

Re: [PATCH v2] usb/uhci: Add support for Aspeed BMC SoCs

On Thu, 25 May 2017, Benjamin Herrenschmidt wrote: > On Wed, 2017-05-24 at 13:58 -0400, Alan Stern wrote: > > Does this new symbol really add anything?  I mean, wouldn't it be just > > as good to use CONFIG_ARCH_ASPEED instead?  It gets used in only one > > place. > > I wanted to split them in

Re: [PATCH v2] usb/uhci: Add support for Aspeed BMC SoCs

On Wed, 2017-05-24 at 13:58 -0400, Alan Stern wrote: > Does this new symbol really add anything?  I mean, wouldn't it be just > as good to use CONFIG_ARCH_ASPEED instead?  It gets used in only one > place. I wanted to split them in case future designs (or different SoC families from Aspeed) do

Re: uas failing on multiple disk access on a jmicron JMS567 bridge

> >> On 22 May 2017, at 14:37, Mathias Nyman >> wrote: >> >> On 22.05.2017 11:48, Christoph Gohle wrote: >>> Hey Mathias, >>> >>> On 19 May 2017, at 09:58, Mathias Nyman wrote: > 4.11 kernel has

Re: [PATCH v2] usb/uhci: Add support for Aspeed BMC SoCs

On Tue, 23 May 2017, Benjamin Herrenschmidt wrote: > The Aspeed 2400/2500 families have a variant of UHCI which requires > some quirks to the driver to work: > > - The register offsets are different. We add a remapping helper. > > - All accesses have to be done via 32-bit loads and stores. We

Re: USB hub clear POWER feature -> device still in 'lsusb' ?!

On Tue, 23 May 2017, Harald Welte wrote: > Dear Linux Kernel USB hackers, > > I'm facing the following overall problem / use case: > > * there is an embedded device, attached to USB, with complex internal > software, which every so often needs to be physically power cycled in > order to

Re: Runtime PM enabled EHCI does not respond to device plugging.

On Wed, 24 May 2017, Kai-Heng Feng wrote: > On Wed, May 24, 2017 at 12:43 AM, Alan Stern > wrote: > >> > >> Output of `cat /sys/kernel/debug/usb/usbmon/1u`: > >> Runtime PM disabled as attachment. > > > > When you say "runtime PM disabled", you mean that it is

Re: [RFC PATCH] staging: typec: Intel WhiskeyCove PMIC USB Type-C PHY driver

On Wed, May 24, 2017 at 05:08:10PM +0200, Greg Kroah-Hartman wrote: > On Wed, May 24, 2017 at 03:54:23PM +0300, Heikki Krogerus wrote: > > Driver for USB Type-C PHY on Intel WhiskeyCove PMIC that > > works with Type-C Port Controller Manager to provide USB > > Power Delivery and USB Type-C

Re: [RFC PATCH] staging: typec: Intel WhiskeyCove PMIC USB Type-C PHY driver

On Wed, May 24, 2017 at 03:54:23PM +0300, Heikki Krogerus wrote: > Driver for USB Type-C PHY on Intel WhiskeyCove PMIC that > works with Type-C Port Controller Manager to provide USB > Power Delivery and USB Type-C functionalities > > Signed-off-by: Heikki Krogerus

Re: [RFC PATCH] usb: optimize acpi companion search for usb port devices

On Wed, May 24, 2017 at 04:11:12PM +0300, Mathias Nyman wrote: > This optimization significantly reduces xhci driver load time. > > In ACPI tables the acpi companion port devices are children of > the hub device. The port devices are identified by their port number > returned by the ACPI _ADR

Re: [RFC PATCH] staging: typec: Intel WhiskeyCove PMIC USB Type-C PHY driver

On Wed, May 24, 2017 at 06:11:20AM -0700, Guenter Roeck wrote: > Hello Heikki, > > On 05/24/2017 05:54 AM, Heikki Krogerus wrote: > > Driver for USB Type-C PHY on Intel WhiskeyCove PMIC that > > works with Type-C Port Controller Manager to provide USB > > Power Delivery and USB Type-C

Re: [RFC PATCH] staging: typec: Intel WhiskeyCove PMIC USB Type-C PHY driver

Hello Heikki, On 05/24/2017 05:54 AM, Heikki Krogerus wrote: Driver for USB Type-C PHY on Intel WhiskeyCove PMIC that works with Type-C Port Controller Manager to provide USB Power Delivery and USB Type-C functionalities Signed-off-by: Heikki Krogerus ---

[RFC PATCH] usb: optimize acpi companion search for usb port devices

This optimization significantly reduces xhci driver load time. In ACPI tables the acpi companion port devices are children of the hub device. The port devices are identified by their port number returned by the ACPI _ADR method. _ADR 0 is reserved for the root hub device. The current

[RFC PATCH] staging: typec: Intel WhiskeyCove PMIC USB Type-C PHY driver

Driver for USB Type-C PHY on Intel WhiskeyCove PMIC that works with Type-C Port Controller Manager to provide USB Power Delivery and USB Type-C functionalities Signed-off-by: Heikki Krogerus --- drivers/staging/typec/Kconfig | 11 +

Re: uas failing on multiple disk access on a jmicron JMS567 bridge

OK. now I am stuck as uas remains blacklisted even after removing the entry in modprobe.d. Why? syslog says: May 24 09:17:49 gserv kernel: [2.288977] usb 2-2: UAS is blacklisted for this device, using usb-storage instead Like this I can’t test. Cheers, Christoph > On 22 May 2017, at

Re: [PATCH 1/3] usb: host: ohci-platform: Add basic runtime PM support

On 23/05/17 17:08, Tony Lindgren wrote: > * Roger Quadros [170523 00:14]: >> On 22/05/17 19:00, Tony Lindgren wrote: >>> --- a/drivers/usb/host/ohci-platform.c >>> +++ b/drivers/usb/host/ohci-platform.c >>> @@ -290,7 +294,14 @@ static int ohci_platform_remove(struct platform_device

Re: [GIT PULL] usb: chipidea bug fixes for v4.12

On Tue, May 23, 2017 at 08:44:56AM +0800, Peter Chen wrote: > The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6: > > Linux 4.12-rc1 (2017-05-13 13:19:49 -0700) > > are available in the git repository at: > >

Re: USB hub clear POWER feature -> device still in 'lsusb' ?!

On Tue, May 23, 2017 at 11:40:58PM +0200, Harald Welte wrote: > Dear Linux Kernel USB hackers, > > I'm facing the following overall problem / use case: > > * there is an embedded device, attached to USB, with complex internal > software, which every so often needs to be physically power cycled

Re: Runtime PM enabled EHCI does not respond to device plugging.

On Wed, May 24, 2017 at 12:43 AM, Alan Stern wrote: >> >> Output of `cat /sys/kernel/debug/usb/usbmon/1u`: >> Runtime PM disabled as attachment. > > When you say "runtime PM disabled", you mean that it is disabled for > the EHCI controller but enabled for other devices,