RE: [PATCH] phy: rcar-gen3-usb2: Add R-Car Gen3 USB2 PHY driver
From: Yoshihiro Shimoda <hidden>
Date: 2015-09-25 12:41:45
Also in:
linux-sh, lkml
Hi Kishon, Thank you for the review! And I'm sorry for the delayed response.
Sent: Friday, September 18, 2015 3:08 PM Hi, On Tuesday 25 August 2015 02:40 PM, Yoshihiro Shimoda wrote:quoted
This patch adds support for R-Car generation 3 USB2 PHY driver. This SoC has 3 EHCI/OHCI channels, and the channel 0 is shared with the HSUSB (USB2.0 peripheral) device.From the description it looks like it's a single PHY with multiple channels. In that case you should have a singe dt node for the PHY provider and each channel should be modelled as the child node of the PHY provider dt node.
Sorry for my lack information.
As my understanding, each EHCI/OHCI channel has a PHY because the following
things are differnce:
- Memory map
- ch0 = 0xee080000
- ch1 = 0xee0a0000
- ch2 = 0xee0c0000
- Clock ("module stop")
- Each channel has a specific clock ("module stop bit").
< snip >quoted
--- /dev/null +++ b/Documentation/devicetree/bindings/phy/rcar-gen3-phy-usb2.txt@@ -0,0 +1,35 @@ +* Renesas R-Car generation 3 USB 2.0 PHY + +This file provides information on what the device node for the R-Car generation +3 USB 2.0 PHY contains. + +Required properties: +- compatible: "renesas,usb2-phy-r8a7795" if the device is a part of an R8A7795 + SoC. +- reg: offset and length of the USB2.0 host register block. +- reg-names: must be "usb2". +- clocks: clock phandle and specifier pair(s). +- #phy-cells: see phy-bindings.txt in the same directory, must be <0>. + +Optional properties: +To use a USB channel where EHCI/OHCI and HSUSB are combined, the device tree +node should set HSUSB properties to reg and reg-names properties: +- reg: offset and length of the HSUSB register block. +- reg-names: must be "hsusb". + +Example (R-Car H3): + + usb-phy@ee080200 { + compatible = "renesas,usb2-phy-r8a7795"; + reg = <0 0xee080200 0 0x6ff>, <0 0xe6590100 0 0x100>; + reg-names = "usb2", "hsusb";hsusb is missing in Documentation.
I wrote the "hsusb" as Optional properties in the Documentation. Or, Is my understanding about your comment wrong? < snip >
quoted
diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig index 0fe9bff..406dc43 100644 --- a/drivers/phy/Kconfig +++ b/drivers/phy/Kconfig@@ -116,6 +116,12 @@ config PHY_RCAR_GEN2 help Support for USB PHY found on Renesas R-Car generation 2 SoCs. +config PHY_RCAR_GEN3_USB2 + tristate "Renesas R-Car generation 3 USB 2.0 PHY driver" + depends on GENERIC_PHYdepends on OF?
Thank you for the point. I will fix it. Best regards, Yoshihiro Shimoda
Thanks Kishon
-- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html