Re: Documentation for USB device interface for power consumption

On Mon, Oct 09, 2017 at 11:36:55AM +0800, Kai Hendry wrote: > Hi there, > > Can't see the /{proc,sys} interface documented in places I expect to be > like https://github.com/torvalds/linux/tree/master/drivers/usb It's documented under Documentation/ABI/ for most of the sysfs stuff, right? > And

Documentation for USB device interface for power consumption

Hi there, Can't see the /{proc,sys} interface documented in places I expect to be like https://github.com/torvalds/linux/tree/master/drivers/usb And the mailing list search is pretty awful: https://marc.info/?l=linux-usb=2=1=power+measure=b My use case is to examine the power draw from my USB

Re: [PATCH 12/12] dt-bindings: usb: mtu3: remove optional pinctrls

On Thu, 2017-10-05 at 17:33 -0500, Rob Herring wrote: > On Thu, Sep 28, 2017 at 08:17:20AM +0800, Chunfeng Yun wrote: > > Remove optional pinctrls due to using FORCE/RG_IDDIG to implement > > manual switch function. > > Another not backwards compatible change. Please explain why that is > okay.

Re: [PATCH 13/13] usb: host: xhci-plat: Use of_device_get_match_data() helper

kbuild just spit out the following warning for this patch: drivers/usb/host/max3421-hcd.c:1707:2-8: preceding lock on line 1702 Error ids grouped by kconfigs: recent_errors └── i386-allmodconfig └── drivers-usb-host-max3421-hcd.c:preceding-lock-on-line I don't really know what it means,

Re: [PATCH 10/12] dt-bindings: usb: mtu3: add a optional property to disable u3ports

On Thu, 2017-10-05 at 17:31 -0500, Rob Herring wrote: > On Thu, Sep 28, 2017 at 08:17:18AM +0800, Chunfeng Yun wrote: > > Add a new optional property to disable u3ports > > > > Signed-off-by: Chunfeng Yun > > --- > > .../devicetree/bindings/usb/mediatek,mtu3.txt

Re: [PATCH 8/9] dt-bindings: usb: mtk-xhci: add a optional property to disable u3ports

On Thu, 2017-10-05 at 17:16 -0500, Rob Herring wrote: > On Wed, Sep 27, 2017 at 05:23:04PM +0800, Chunfeng Yun wrote: > > Add a new optional property to disable u3ports > > > > Signed-off-by: Chunfeng Yun > > --- > > .../devicetree/bindings/usb/mediatek,mtk-xhci.txt

Re: [PATCH 01/12] usb: mtu3: fix error return code in ssusb_gadget_init()

On Sat, 2017-09-30 at 16:00 +0300, Sergei Shtylyov wrote: > Hello! > > On 9/28/2017 3:17 AM, Chunfeng Yun wrote: > > > When fail to get irq number, platform_get_irq() may return > > Failing. IRQ. :-) I'll modify it, thank you > > > -EPROBE_DEFER, but we ignore it and always return

[RFC usb-next v5 1/3] dt-bindings: usb: add the documentation for USB root-hub

A USB root-hub may have several PHYs which need to be configured before the root-hub starts working. This adds the documentation for such a USB root-hub as well as a hint regarding the child-nodes on XHCI controllers which can include the roothub. Signed-off-by: Martin Blumenstingl

[RFC usb-next v5 0/3] initialize (multiple) PHYs on the roothub

This series is the outcome of a discussion with Felipe Balbi, see [0] and [1] as well as Mathias Nyman, see [7] and [8]. The quick-summary of this is: - dwc3 already takes one USB2 and one USB3 PHY and initializes these correct - some other HCI platform drivers (like ehci-platform.c, xhci-mtk.c

[RFC usb-next v5 2/3] usb: core: add a wrapper for the USB PHYs on the root-hub

Many SoC platforms have separate devices for the USB PHY which are registered through the generic PHY framework. These PHYs have to be enabled to make the USB controller actually work. They also have to be disabled again on shutdown/suspend. Currently (at least) the following HCI platform drivers

[RFC usb-next v5 3/3] usb: core: hcd: integrate the PHY roothub wrapper

This integrates the PHY roothub wrapper into the core hcd infrastructure. Multiple PHYs which are part of the roothub devicetree node (which is a sub-node of the sysdev's node) are now managed (= powered on/off when needed), by the new usb_phy_roothub code. One example where this is required is

VL805 xHCI DMA read faults

Hi, I've been having DMA read faults with my VL805 xHCI controller when the Intel IOMMU is turned on: xhci_hcd :03:00.0: xHCI Host Controller xhci_hcd :03:00.0: new USB bus registered, assigned bus number 2 DMAR: DRHD: handling fault status reg 3 DMAR: [DMA Read] Request