On Mon, Feb 04, 2013 at 03:58:55PM +0000, Roger Quadros wrote: > Allows the OMAP EHCI controller to be specified via device tree. > > Signed-off-by: Roger Quadros <rogerq@xxxxxx> > --- > .../devicetree/bindings/usb/omap-ehci.txt | 34 ++++++++++++++++++ > drivers/usb/host/ehci-omap.c | 36 +++++++++++++++++++- > 2 files changed, 69 insertions(+), 1 deletions(-) > create mode 100644 Documentation/devicetree/bindings/usb/omap-ehci.txt > > diff --git a/Documentation/devicetree/bindings/usb/omap-ehci.txt b/Documentation/devicetree/bindings/usb/omap-ehci.txt > new file mode 100644 > index 0000000..90e6e3a > --- /dev/null > +++ b/Documentation/devicetree/bindings/usb/omap-ehci.txt > @@ -0,0 +1,34 @@ > +OMAP HS USB EHCI controller > + > +This device is usually the child of the omap-usb-host > +Documentation/devicetree/bindings/mfd/omap-usb-host.txt > + > +Required properties: > + > +- compatible: should be "ti,omap-ehci" > +- reg: should contain one register range i.e. start and length > +- interrupt-parent: phandle to the interrupt controller > +- interrupts: description of the interrupt line > + > +Optional properties: > + > +- phy: list of phandles to PHY nodes. > + This property is required if at least one of the ports are in > + PHY mode i.e. OMAP_EHCI_PORT_MODE_PHY Any reason for not calling this "phys", given it's a list? [...] Thanks, Mark. -- 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
