| Message ID | 1363609781-4045-2-git-send-email-vbyravarasu@nvidia.com |
|---|---|
| State | Superseded, archived |
| Headers | show |
Hi, On Monday 18 March 2013 05:59 PM, Venu Byravarasu wrote: > The existing Tegra USB bindings have a few issues: > > 1) Many properties are documented as being part of the EHCI controller > node, yet they apply more to the PHY device. They should be moved. > > 2) Some registers in PHY1 are shared with PHY3, and hence PHY3 needs a > reg entry to point at PHY1's register space. We can't assume the PHY1 > driver is present, so the PHY3 driver will directly access those > registers. > > 3) The list of clocks required by the PHY was missing some required > entries. > > This patch fixes the binding definition to resolve these issues. > > Signed-off-by: Venu Byravarasu <vbyravarasu@nvidia.com> > --- > .../bindings/usb/nvidia,tegra20-ehci.txt | 27 +++---------------- > .../bindings/usb/nvidia,tegra20-usb-phy.txt | 27 +++++++++++++++++-- > 2 files changed, 29 insertions(+), 25 deletions(-) > > diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt b/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt > index 34c9528..df09330 100644 > --- a/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt > +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt > @@ -6,27 +6,10 @@ Practice : Universal Serial Bus" with the following modifications > and additions : > > Required properties : > - - compatible : Should be "nvidia,tegra20-ehci" for USB controllers > - used in host mode. > - - phy_type : Should be one of "ulpi" or "utmi". > - - nvidia,vbus-gpio : If present, specifies a gpio that needs to be > - activated for the bus to be powered. > - - nvidia,phy : phandle of the PHY instance, the controller is connected to. > - > -Required properties for phy_type == ulpi: > - - nvidia,phy-reset-gpio : The GPIO used to reset the PHY. > + - compatible : Should be "nvidia,tegra20-ehci". > + - nvidia,phy : phandle of the PHY that the controller is connected to. > + - clocks : Contains a single entry which defines the USB controller's clock. > > Optional properties: > - - dr_mode : dual role mode. Indicates the working mode for > - nvidia,tegra20-ehci compatible controllers. Can be "host", "peripheral", > - or "otg". Default to "host" if not defined for backward compatibility. > - host means this is a host controller > - peripheral means it is device controller > - otg means it can operate as either ("on the go") > - - nvidia,has-legacy-mode : boolean indicates whether this controller can > - operate in legacy mode (as APX 2500 / 2600). In legacy mode some > - registers are accessed through the APB_MISC base address instead of > - the USB controller. Since this is a legacy issue it probably does not > - warrant a compatible string of its own. > - - nvidia,needs-double-reset : boolean is to be set for some of the Tegra2 > - USB ports, which need reset twice due to hardware issues. > + - nvidia,needs-double-reset : boolean is to be set for some of the Tegra20 > + USB ports, which need reset twice due to hardware issues. > diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt b/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt > index 6bdaba2..7ceccd3 100644 > --- a/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt > +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt > @@ -4,8 +4,24 @@ The device node for Tegra SOC USB PHY: > > Required properties : > - compatible : Should be "nvidia,tegra20-usb-phy". > - - reg : Address and length of the register set for the USB PHY interface. > - - phy_type : Should be one of "ulpi" or "utmi". > + - reg : Defines the following set of registers, in the order listed: > + - The PHY's own register set. > + Always present. > + - The register set of the PHY containing the UTMI pad control registers. > + Present if-and-only-if phy_type == utmi. > + - phy_type : Should be one of "utmi", "ulpi" or "hsic". dt property names generally dont have "_". Thanks Kishon -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
> -----Original Message----- > From: kishon [mailto:kishon@ti.com] > Sent: Wednesday, March 20, 2013 4:49 PM > To: Venu Byravarasu > Cc: gregkh@linuxfoundation.org; stern@rowland.harvard.edu; > balbi@ti.com; linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org; > swarren@wwwdotorg.org; linux-tegra@vger.kernel.org; devicetree- > discuss@lists.ozlabs.org > Subject: Re: [PATCH 1/7] ARM: tegra: finalize USB EHCI and PHY bindings > > Hi, > > On Monday 18 March 2013 05:59 PM, Venu Byravarasu wrote: > > The existing Tegra USB bindings have a few issues: > > > > 1) Many properties are documented as being part of the EHCI controller > > node, yet they apply more to the PHY device. They should be moved. > > > > 2) Some registers in PHY1 are shared with PHY3, and hence PHY3 needs a > > reg entry to point at PHY1's register space. We can't assume the PHY1 > > driver is present, so the PHY3 driver will directly access those > > registers. > > > > 3) The list of clocks required by the PHY was missing some required > > entries. > > > > This patch fixes the binding definition to resolve these issues. > > > > Signed-off-by: Venu Byravarasu <vbyravarasu@nvidia.com> > > --- > > .../bindings/usb/nvidia,tegra20-ehci.txt | 27 +++---------------- > > .../bindings/usb/nvidia,tegra20-usb-phy.txt | 27 > +++++++++++++++++-- > > 2 files changed, 29 insertions(+), 25 deletions(-) > > > > diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt > b/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt > > index 34c9528..df09330 100644 > > --- a/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt > > +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt > > @@ -6,27 +6,10 @@ Practice : Universal Serial Bus" with the following > modifications > > and additions : > > > > Required properties : > > - - compatible : Should be "nvidia,tegra20-ehci" for USB controllers > > - used in host mode. > > - - phy_type : Should be one of "ulpi" or "utmi". > > > > Optional properties: > > - - dr_mode : dual role mode. Indicates the working mode for > > index 6bdaba2..7ceccd3 100644 > > --- a/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt > > +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt > > @@ -4,8 +4,24 @@ The device node for Tegra SOC USB PHY: > > > > Required properties : > > + - phy_type : Should be one of "utmi", "ulpi" or "hsic". > > dt property names generally dont have "_". Thanks Kishon, for your comments. Is it mandatory or optional? If it is mandatory, then I might have to change dr_mode as well along with phy_type. > > Thanks > Kishon -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 03/20/2013 06:15 AM, Venu Byravarasu wrote: >> -----Original Message----- >> From: kishon [mailto:kishon@ti.com] >> Sent: Wednesday, March 20, 2013 4:49 PM >> To: Venu Byravarasu >> Cc: gregkh@linuxfoundation.org; stern@rowland.harvard.edu; >> balbi@ti.com; linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org; >> swarren@wwwdotorg.org; linux-tegra@vger.kernel.org; devicetree- >> discuss@lists.ozlabs.org >> Subject: Re: [PATCH 1/7] ARM: tegra: finalize USB EHCI and PHY bindings >> >> Hi, >> >> On Monday 18 March 2013 05:59 PM, Venu Byravarasu wrote: >>> The existing Tegra USB bindings have a few issues: >>> >>> 1) Many properties are documented as being part of the EHCI controller >>> node, yet they apply more to the PHY device. They should be moved. >>> >>> 2) Some registers in PHY1 are shared with PHY3, and hence PHY3 needs a >>> reg entry to point at PHY1's register space. We can't assume the PHY1 >>> driver is present, so the PHY3 driver will directly access those >>> registers. >>> >>> 3) The list of clocks required by the PHY was missing some required >>> entries. >>> >>> This patch fixes the binding definition to resolve these issues. >>> >>> Signed-off-by: Venu Byravarasu <vbyravarasu@nvidia.com> >>> --- >>> .../bindings/usb/nvidia,tegra20-ehci.txt | 27 +++---------------- >>> .../bindings/usb/nvidia,tegra20-usb-phy.txt | 27 >> +++++++++++++++++-- >>> 2 files changed, 29 insertions(+), 25 deletions(-) >>> >>> diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt >> b/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt >>> index 34c9528..df09330 100644 >>> --- a/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt >>> +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt >>> @@ -6,27 +6,10 @@ Practice : Universal Serial Bus" with the following >> modifications >>> and additions : >>> >>> Required properties : >>> - - compatible : Should be "nvidia,tegra20-ehci" for USB controllers >>> - used in host mode. >>> - - phy_type : Should be one of "ulpi" or "utmi". >>> >>> Optional properties: >>> - - dr_mode : dual role mode. Indicates the working mode for > >>> index 6bdaba2..7ceccd3 100644 >>> --- a/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt >>> +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt >>> @@ -4,8 +4,24 @@ The device node for Tegra SOC USB PHY: >>> >>> Required properties : >>> + - phy_type : Should be one of "utmi", "ulpi" or "hsic". >> >> dt property names generally dont have "_". > > Thanks Kishon, for your comments. > Is it mandatory or optional? > If it is mandatory, then I might have to change dr_mode as well along with phy_type. This rule is basically mandatory for *new* property definitions. However, both phy_type and dr_mode are properties that already exist and have historical precedence for their naming. So, I don't think we can change them. In fact, IIRC, someone even posted some patches to provide a common set of parsing functions for those properties, and I assume those patches use the existing names with _ in them. The patches aren't applied yet though, I think. (Venu, we already discussed this rule downstream) -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" 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/nvidia,tegra20-ehci.txt b/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt index 34c9528..df09330 100644 --- a/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt @@ -6,27 +6,10 @@ Practice : Universal Serial Bus" with the following modifications and additions : Required properties : - - compatible : Should be "nvidia,tegra20-ehci" for USB controllers - used in host mode. - - phy_type : Should be one of "ulpi" or "utmi". - - nvidia,vbus-gpio : If present, specifies a gpio that needs to be - activated for the bus to be powered. - - nvidia,phy : phandle of the PHY instance, the controller is connected to. - -Required properties for phy_type == ulpi: - - nvidia,phy-reset-gpio : The GPIO used to reset the PHY. + - compatible : Should be "nvidia,tegra20-ehci". + - nvidia,phy : phandle of the PHY that the controller is connected to. + - clocks : Contains a single entry which defines the USB controller's clock. Optional properties: - - dr_mode : dual role mode. Indicates the working mode for - nvidia,tegra20-ehci compatible controllers. Can be "host", "peripheral", - or "otg". Default to "host" if not defined for backward compatibility. - host means this is a host controller - peripheral means it is device controller - otg means it can operate as either ("on the go") - - nvidia,has-legacy-mode : boolean indicates whether this controller can - operate in legacy mode (as APX 2500 / 2600). In legacy mode some - registers are accessed through the APB_MISC base address instead of - the USB controller. Since this is a legacy issue it probably does not - warrant a compatible string of its own. - - nvidia,needs-double-reset : boolean is to be set for some of the Tegra2 - USB ports, which need reset twice due to hardware issues. + - nvidia,needs-double-reset : boolean is to be set for some of the Tegra20 + USB ports, which need reset twice due to hardware issues. diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt b/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt index 6bdaba2..7ceccd3 100644 --- a/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt @@ -4,8 +4,24 @@ The device node for Tegra SOC USB PHY: Required properties : - compatible : Should be "nvidia,tegra20-usb-phy". - - reg : Address and length of the register set for the USB PHY interface. - - phy_type : Should be one of "ulpi" or "utmi". + - reg : Defines the following set of registers, in the order listed: + - The PHY's own register set. + Always present. + - The register set of the PHY containing the UTMI pad control registers. + Present if-and-only-if phy_type == utmi. + - phy_type : Should be one of "utmi", "ulpi" or "hsic". + - clocks : Defines the clocks listed in the clock-names property. + - clock-names : The following clock names must be present: + - reg: The clock needed to access the PHY's own registers. This is the + associated EHCI controller's clock. Always present. + - pll_u: PLL_U. Always present. + - timer: The timeout clock (clk_m). Present if phy_type == utmi. + - utmi-pads: The clock needed to access the UTMI pad control registers. + Present if phy_type == utmi. + - ulpi-link: The clock Tegra provides to the ULPI PHY (cdev2). + Present if phy_type == ulpi, and ULPI link mode is in use. + - nvidia,vbus-gpio : If present, specifies a GPIO that needs to be + activated for the bus to be powered. Required properties for phy_type == ulpi: - nvidia,phy-reset-gpio : The GPIO used to reset the PHY. @@ -14,4 +30,9 @@ Optional properties: - nvidia,has-legacy-mode : boolean indicates whether this controller can operate in legacy mode (as APX 2500 / 2600). In legacy mode some registers are accessed through the APB_MISC base address instead of - the USB controller. \ No newline at end of file + the USB controller. + - dr_mode : dual role mode. Indicates the working mode for the PHY. Can be + "host", "gadget", or "otg". Defaults to "host" if not defined. + host means this is a host controller + gadget means it is device controller + otg means it can operate as either ("on the go")
The existing Tegra USB bindings have a few issues: 1) Many properties are documented as being part of the EHCI controller node, yet they apply more to the PHY device. They should be moved. 2) Some registers in PHY1 are shared with PHY3, and hence PHY3 needs a reg entry to point at PHY1's register space. We can't assume the PHY1 driver is present, so the PHY3 driver will directly access those registers. 3) The list of clocks required by the PHY was missing some required entries. This patch fixes the binding definition to resolve these issues. Signed-off-by: Venu Byravarasu <vbyravarasu@nvidia.com> --- .../bindings/usb/nvidia,tegra20-ehci.txt | 27 +++---------------- .../bindings/usb/nvidia,tegra20-usb-phy.txt | 27 +++++++++++++++++-- 2 files changed, 29 insertions(+), 25 deletions(-)