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