From: Subbaraya Sundeep Bhatta <subbaraya.sundeep.bhatta@xilinx.com>
To: balbi@ti.com, peter.chen@freescale.com,
devicetree@vger.kernel.org, kishon@ti.com
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, punnaia@xilinx.com,
Subbaraya Sundeep Bhatta <sbhatta@xilinx.com>
Subject: [RFC PATCH 1/2] usb: doc: Add bindings for ULPI platform driver
Date: Wed, 23 Sep 2015 18:24:01 +0530 [thread overview]
Message-ID: <1443012841-13673-1-git-send-email-sbhatta@xilinx.com> (raw)
This patch adds binding doc info for generic ULPI PHYs
platform driver.
Signed-off-by: Subbaraya Sundeep Bhatta <sbhatta@xilinx.com>
---
.../devicetree/bindings/usb/ulpi-platform-phy.txt | 34 ++++++++++++++++++++
1 files changed, 34 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/usb/ulpi-platform-phy.txt
diff --git a/Documentation/devicetree/bindings/usb/ulpi-platform-phy.txt b/Documentation/devicetree/bindings/usb/ulpi-platform-phy.txt
new file mode 100644
index 0000000..7b8cbb4
--- /dev/null
+++ b/Documentation/devicetree/bindings/usb/ulpi-platform-phy.txt
@@ -0,0 +1,34 @@
+Platform driver for generic ULPI PHYs
+
+Required properties:
+- compatible : Should be "ulpi-phy"
+- reg : Physical base address and size of the USB
+ controller registers map to which this PHY
+ is connected.
+- view-port : Should contain viewport register offset of the
+ USB controller to which this PHY is connected
+Optional properties:
+- drv-vbus : required if turning VBUS on/off has to be driven
+ by writing to PHY. This feature depends on board
+ design.
+
+Example:
+Below example shows the PHY binding for Chipidea USB controller which has
+ulpi viewport register at 0x0170
+
+ usb_phy0: phy0 {
+ compatible = "ulpi-phy";
+ reg = <0xe0002000 0x1000>;
+ view-port = <0x0170>;
+ drv-vbus;
+ };
+
+ usb0: usb@e0002000 {
+ compatible = "chipidea,usb2";
+ interrupt-parent = <&intc>;
+ interrupts = <0 21 4>;
+ reg = <0xe0002000 0x1000>;
+ phy_type = "ulpi";
+ dr_mode = "host";
+ usb-phy = <&usb_phy0>;
+ };
--
1.7.1
next reply other threads:[~2015-09-23 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 12:54 Subbaraya Sundeep Bhatta [this message]
[not found] ` <1443012841-13673-1-git-send-email-sbhatta-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2015-09-24 9:10 ` [RFC PATCH 1/2] usb: doc: Add bindings for ULPI platform driver Peter Chen
2015-09-24 9:26 ` Subbaraya Sundeep Bhatta
2015-09-24 16:18 ` Rob Herring
2015-09-30 16:18 ` Felipe Balbi
[not found] ` <20150930161803.GI32625-HgARHv6XitJaoMGHk7MhZQC/G2K4zDHf@public.gmane.org>
2015-10-11 11:15 ` punnaiah choudary kalluri
[not found] ` <CAGnW=Bb0pdv7i1N=WqZoQLDUpuGw=Xq=cM5ir2Ow25pUDYtvEA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-11 14:40 ` Kishon Vijay Abraham I
[not found] ` <561A74E6.9050406-l0cyMroinI0@public.gmane.org>
2015-10-28 11:55 ` Subbaraya Sundeep Bhatta
2015-09-24 16:14 ` Rob Herring
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=1443012841-13673-1-git-send-email-sbhatta@xilinx.com \
--to=subbaraya.sundeep.bhatta@xilinx.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@freescale.com \
--cc=punnaia@xilinx.com \
--cc=sbhatta@xilinx.com \
/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;
as well as URLs for NNTP newsgroup(s).