On 4/7/2016 3:32 PM, Purna Chandra Mandal wrote:
Document devicetree binding for the USB controller and USB Phy found on Microchip PIC32 class devices. Signed-off-by: Purna Chandra Mandal <purna.mandal@xxxxxxxxxxxxx> --- Changes in v2: None .../bindings/usb/microchip,pic32-musb.txt | 67 ++++++++++++++++++++++ 1 file changed, 67 insertions(+) create mode 100644 Documentation/devicetree/bindings/usb/microchip,pic32-musb.txt diff --git a/Documentation/devicetree/bindings/usb/microchip,pic32-musb.txt b/Documentation/devicetree/bindings/usb/microchip,pic32-musb.txt new file mode 100644 index 0000000..e1cec9d --- /dev/null +++ b/Documentation/devicetree/bindings/usb/microchip,pic32-musb.txt @@ -0,0 +1,67 @@ +Microchip PIC32 MUSB DRC/OTG controller +------------------------------------------- + +Required properties: + - compatible : should be "microchip,pic32mzda-usb". + - reg : offset and length of "MUSB Core Registers" and + "USB Clock & Reset Registers". + - reg-names : should be "mc", and "usbcr" in order + - clocks : clock specifier for the musb controller clock + - clock-names : should be "usb_clk" + - interrupts : interrupt number for MUSB Core General interrupt + and DMA interrupt + - interrupt-names : must be "mc" and "dma" in order. + - phys : phy specifier for the otg phy. + - dr_mode : should be one of "host", "peripheral" or "otg". + - mentor,multipoint: Should be "1" indicating the musb controller supports + multipoint. This is MUSB configuration-specific setting. + - mentor,num-eps : Specifies the number of endpoints. This is also a + MUSB configuration-specific setting. Should be set to "8". + - mentor,ram-bits : Specifies the ram address size. Should be set to "11". + - mentor,power : Should be "500". This signifies the controller can supply + up to 500mA when operating in host mode. + - phys : phandle of the USB phy.
Just noticed that "phys" is described twice. :-/ MBR, Sergei -- 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
