On Tue, Jul 12, 2016 at 02:35:18PM +0200, Rafał Miłecki wrote: > Hi, > > I was working on an "usbport" LED trigger driver and specifying its > default state in DT. I realized I can't really determine numbering of > USB ports on any device as it depends on compiled drivers and the > loading orders. > > It means that my physical USB port can be e.g. 1-1 or 2-1 depending on > my current config/setup. I needed a way to specify a particular HCD in > DT and then hardcode port number (as this part doesn't change). > I have a question: What does your "usbport" LED trigger for? What kinds of information you would like to show on LED? Peter > These 2 patches add providers to usb core subsystem. I successfully > tested it with "usbport" trigger and generic-ohci, generic-ehci & > generic-xhci. > > The last (third) patch is not supposed to be applied, it's used only as > a proof and example of how providers can be used. > > If there is anything wrong with this idea/implementation, please let me > know. > > Rafał Miłecki (2): > usb: core: add support for HCD providers > ohci-platform: register HCD provider > > drivers/usb/core/Makefile | 1 + > drivers/usb/core/provider.c | 79 ++++++++++++++++++++++++++++++++++++++++ > drivers/usb/host/ohci-platform.c | 9 +++++ > include/linux/usb/provider.h | 39 ++++++++++++++++++++ > 4 files changed, 128 insertions(+) > create mode 100644 drivers/usb/core/provider.c > create mode 100644 include/linux/usb/provider.h > > -- > 1.8.4.5 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Best Regards, Peter Chen -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
