| Message ID | 392aceb635682614b8509b4090943f806b3236f2.1351870620.git.afzal@ti.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Fri, Nov 02, 2012 at 10:02:47PM +0530, Afzal Mohammed wrote: > OMAP2+ family of devices are now obtaining resources via DT, earlier > it was obtained from hwmod. Update binding document accrodingly, while > at it add example. > > Signed-off-by: Afzal Mohammed <afzal@ti.com> > --- > .../devicetree/bindings/usb/am33xx-usb.txt | 21 +++++++++++++++++++++ > 1 file changed, 21 insertions(+) > > diff --git a/Documentation/devicetree/bindings/usb/am33xx-usb.txt b/Documentation/devicetree/bindings/usb/am33xx-usb.txt > index a922505..6b7e3bd 100644 > --- a/Documentation/devicetree/bindings/usb/am33xx-usb.txt > +++ b/Documentation/devicetree/bindings/usb/am33xx-usb.txt > @@ -1,5 +1,7 @@ > AM33XX MUSB GLUE > - compatible : Should be "ti,musb-am33xx" > + - reg : offset and length of register sets, first usbss, then for musb instances > + - interrupts : usbss, musb instance interrupts in order > - ti,hwmods : must be "usb_otg_hs" > - multipoint : Should be "1" indicating the musb controller supports > multipoint. This is a MUSB configuration-specific setting. > @@ -12,3 +14,22 @@ AM33XX MUSB GLUE > represents PERIPHERAL. > - power : Should be "250". This signifies the controller can supply upto > 500mA when operating in host mode. > + > +Example: > + > +usb_otg_hs@47400000 { this should be usb@47400000. > + compatible = "ti,musb-am33xx"; > + reg = <0x47400000 0x1000 /* usbss */ > + 0x47401000 0x800 /* musb instance 0 */ > + 0x47401800 0x800>; /* musb instance 1 */ > + interrupts = <17 /* usbss */ > + 18 /* musb instance 0 */ > + 19>; /* musb instance 1 */ > + multipoint = <1>; > + num-eps = <16>; > + ram-bits = <12>; > + port0-mode = <3>; > + port1-mode = <3>; > + power = <250>; > + ti,hwmods = "usb_otg_hs"; > +}; > -- > 1.7.12 >
Hi Balbi, On Tuesday 06 November 2012 06:32 PM, Felipe Balbi wrote: > On Fri, Nov 02, 2012 at 10:02:47PM +0530, Afzal Mohammed wrote: >> +Example: >> + >> +usb_otg_hs@47400000 { > this should be usb@47400000. Updated version with the above change has been posted. Regards Afzal -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/usb/am33xx-usb.txt b/Documentation/devicetree/bindings/usb/am33xx-usb.txt index a922505..6b7e3bd 100644 --- a/Documentation/devicetree/bindings/usb/am33xx-usb.txt +++ b/Documentation/devicetree/bindings/usb/am33xx-usb.txt @@ -1,5 +1,7 @@ AM33XX MUSB GLUE - compatible : Should be "ti,musb-am33xx" + - reg : offset and length of register sets, first usbss, then for musb instances + - interrupts : usbss, musb instance interrupts in order - ti,hwmods : must be "usb_otg_hs" - multipoint : Should be "1" indicating the musb controller supports multipoint. This is a MUSB configuration-specific setting. @@ -12,3 +14,22 @@ AM33XX MUSB GLUE represents PERIPHERAL. - power : Should be "250". This signifies the controller can supply upto 500mA when operating in host mode. + +Example: + +usb_otg_hs@47400000 { + compatible = "ti,musb-am33xx"; + reg = <0x47400000 0x1000 /* usbss */ + 0x47401000 0x800 /* musb instance 0 */ + 0x47401800 0x800>; /* musb instance 1 */ + interrupts = <17 /* usbss */ + 18 /* musb instance 0 */ + 19>; /* musb instance 1 */ + multipoint = <1>; + num-eps = <16>; + ram-bits = <12>; + port0-mode = <3>; + port1-mode = <3>; + power = <250>; + ti,hwmods = "usb_otg_hs"; +};
OMAP2+ family of devices are now obtaining resources via DT, earlier it was obtained from hwmod. Update binding document accrodingly, while at it add example. Signed-off-by: Afzal Mohammed <afzal@ti.com> --- .../devicetree/bindings/usb/am33xx-usb.txt | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+)