rcar-gen3-phy-usb2.txt 1.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. * Renesas R-Car generation 3 USB 2.0 PHY
  2. This file provides information on what the device node for the R-Car generation
  3. 3 USB 2.0 PHY contains.
  4. Required properties:
  5. - compatible: "renesas,usb2-phy-r8a7795" if the device is a part of an R8A7795
  6. SoC.
  7. "renesas,usb2-phy-r8a7796" if the device is a part of an R8A7796
  8. SoC.
  9. "renesas,usb2-phy-r8a77965" if the device is a part of an
  10. R8A77965 SoC.
  11. "renesas,usb2-phy-r8a77990" if the device is a part of an
  12. R8A77990 SoC.
  13. "renesas,usb2-phy-r8a77995" if the device is a part of an
  14. R8A77995 SoC.
  15. "renesas,rcar-gen3-usb2-phy" for a generic R-Car Gen3 compatible device.
  16. When compatible with the generic version, nodes must list the
  17. SoC-specific version corresponding to the platform first
  18. followed by the generic version.
  19. - reg: offset and length of the partial USB 2.0 Host register block.
  20. - clocks: clock phandle and specifier pair(s).
  21. - #phy-cells: see phy-bindings.txt in the same directory, must be <0>.
  22. Optional properties:
  23. To use a USB channel where USB 2.0 Host and HSUSB (USB 2.0 Peripheral) are
  24. combined, the device tree node should set interrupt properties to use the
  25. channel as USB OTG:
  26. - interrupts: interrupt specifier for the PHY.
  27. - vbus-supply: Phandle to a regulator that provides power to the VBUS. This
  28. regulator will be managed during the PHY power on/off sequence.
  29. Example (R-Car H3):
  30. usb-phy@ee080200 {
  31. compatible = "renesas,usb2-phy-r8a7795", "renesas,rcar-gen3-usb2-phy";
  32. reg = <0 0xee080200 0 0x700>;
  33. interrupts = <GIC_SPI 108 IRQ_TYPE_LEVEL_HIGH>;
  34. clocks = <&cpg CPG_MOD 703>;
  35. };
  36. usb-phy@ee0a0200 {
  37. compatible = "renesas,usb2-phy-r8a7795", "renesas,rcar-gen3-usb2-phy";
  38. reg = <0 0xee0a0200 0 0x700>;
  39. clocks = <&cpg CPG_MOD 702>;
  40. };