From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/5] phy: DT binding documentation for qoriq usb 2.0 phy
Date: Fri, 15 Jul 2016 19:35:03 -0500 [thread overview]
Message-ID: <20160716003503.GA6930@rob-hp-laptop> (raw)
In-Reply-To: <1468038656-10345-5-git-send-email-rajesh.bhagat@nxp.com>
On Sat, Jul 09, 2016 at 10:00:55AM +0530, Rajesh Bhagat wrote:
> Describes the qoriq usb 2.0 phy driver binding, currently used
> for LS1021A and LS1012A platform.
>
> Signed-off-by: Rajesh Bhagat <rajesh.bhagat@nxp.com>
> ---
> Changes in v2:
> - Adds DT binding documentation for qoriq usb 2.0 phy
> - Changed the compatible string to fsl,qoriq-usb2-phy
>
> .../devicetree/bindings/phy/qoriq-usb2-phy.txt | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/qoriq-usb2-phy.txt
>
> diff --git a/Documentation/devicetree/bindings/phy/qoriq-usb2-phy.txt b/Documentation/devicetree/bindings/phy/qoriq-usb2-phy.txt
> new file mode 100644
> index 0000000..f043855
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/qoriq-usb2-phy.txt
> @@ -0,0 +1,22 @@
> +QorIQ SoC USB 2.0 PHY
> +
> +Required properties:
> + - compatible: should be "fsl,qoriq-usb2-phy",
> + Wherever applicable, the version of the USB PHY should
> + also be mentioned (for eg. fsl,qoriq-usb2-phy-vX.Y).
> + where, X = Phy vendor(Legacy = 1, NXP = 2) and Y = PHY version
What does Legacy mean? FSL?
Use SoC specific compatible strings.
> + - reg : Address and length of the usb phy control register set.
> + - phy_type : For multi port host USB controllers, should be one of
> + "ulpi", or "serial". For dual role USB controllers, should be
> + one of "ulpi", "utmi", "utmi_wide", or "serial".
> +
> +The main purpose of this PHY driver is to enable the USB PHY reference clock
> +gate on the QorIQ SOC for USB2 PHY OR implement errata workaround in
> +future. Otherwise it is just an NOP PHY driver.
> +
> +usbphy0: usbphy at 8600000 {
> + compatible = "fsl,qoriq-usb2-phy" "fsl,qoriq-usb2-phy-vX.Y";
most specific first.
> + reg = <0x0 0x8600000 0x0 0x1000>;
> + #phy-cells = <0>;
> + phy_type = "ulpi";
> +};
prev parent reply other threads:[~2016-07-16 0:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1468038656-10345-1-git-send-email-rajesh.bhagat@nxp.com>
[not found] ` <1468038656-10345-2-git-send-email-rajesh.bhagat@nxp.com>
2016-07-09 5:53 ` [PATCH v2 1/5] drivers: usb: chipidea: Add qoriq platform driver kbuild test robot
2016-07-09 5:59 ` kbuild test robot
2016-07-09 6:13 ` kbuild test robot
2016-07-11 6:43 ` Peter Chen
2016-07-12 3:59 ` Rajesh Bhagat
2016-07-15 7:13 ` Peter Chen
2016-07-15 8:13 ` Rajesh Bhagat
[not found] ` <1468038656-10345-3-git-send-email-rajesh.bhagat@nxp.com>
2016-07-11 6:48 ` [PATCH v2 2/5] usb: DT binding documentation for qoriq usb 2.0 controller Peter Chen
2016-07-12 3:59 ` Rajesh Bhagat
2016-07-15 7:15 ` Peter Chen
2016-07-15 8:13 ` Rajesh Bhagat
2016-07-16 0:28 ` Rob Herring
[not found] ` <1468038656-10345-4-git-send-email-rajesh.bhagat@nxp.com>
2016-07-11 6:54 ` [PATCH v2 3/5] drivers: usb: phy: Add qoriq usb 2.0 phy driver support Peter Chen
2016-07-12 3:59 ` Rajesh Bhagat
[not found] ` <1468038656-10345-5-git-send-email-rajesh.bhagat@nxp.com>
2016-07-16 0:35 ` Rob Herring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160716003503.GA6930@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox