From: George Cherian <george.cherian@ti.com>
To: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org
Cc: s.nawrocki@samsung.com, tony@atomide.com, george.cherian@ti.com,
gregkh@linuxfoundation.org, kishon@ti.com, rob@landley.net,
galak@codeaurora.org, ijc+devicetree@hellion.org.uk,
mark.rutland@arm.com, pawel.moll@arm.com, robh+dt@kernel.org
Subject: [PATCH v2 3/3] phy: omap-usb2: Add different compatible for OMAP5
Date: Thu, 6 Mar 2014 18:11:54 +0530 [thread overview]
Message-ID: <1394109714-31228-4-git-send-email-george.cherian@ti.com> (raw)
In-Reply-To: <1394109714-31228-1-git-send-email-george.cherian@ti.com>
Add a new compatible for OMAP5 since it does not use any of the
OTG operations as of now.
HAS_SRP and SET_VBUS functionalities are used only for OMAP4.
Update the Documentation also to add new comaptible.
Signed-off-by: George Cherian <george.cherian@ti.com>
---
Documentation/devicetree/bindings/usb/usb-phy.txt | 3 ++-
drivers/phy/phy-omap-usb2.c | 9 +++++++++
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/usb/usb-phy.txt b/Documentation/devicetree/bindings/usb/usb-phy.txt
index 03de61a5..ec199a5 100644
--- a/Documentation/devicetree/bindings/usb/usb-phy.txt
+++ b/Documentation/devicetree/bindings/usb/usb-phy.txt
@@ -4,7 +4,8 @@ OMAP USB2 PHY
Required properties:
- compatible: Should be either of
- * "ti,omap-usb2" for OMAP4 and OMAP5
+ * "ti,omap-usb2" for OMAP4
+ * "ti,omap5-usb2" for OMAP5
* "ti,dra7x-usb2" for DRA7
* "ti,am437x-usb2" for AM437x
- reg : Address and length of the register set for the device.
diff --git a/drivers/phy/phy-omap-usb2.c b/drivers/phy/phy-omap-usb2.c
index b220202..3cc4aba 100644
--- a/drivers/phy/phy-omap-usb2.c
+++ b/drivers/phy/phy-omap-usb2.c
@@ -154,6 +154,11 @@ static const struct usb_phy_data omap_usb2_data = {
.flags = OMAP_USB2_HAS_START_SRP | OMAP_USB2_HAS_SET_VBUS,
};
+static const struct usb_phy_data omap5_usb2_data = {
+ .label = "omap5_usb2",
+ .flags = 0,
+};
+
static const struct usb_phy_data dra7x_usb2_data = {
.label = "dra7x_usb2",
.flags = OMAP_USB2_CALIBRATE_FALSE_DISCONNECT,
@@ -170,6 +175,10 @@ static const struct of_device_id omap_usb2_id_table[] = {
.data = &omap_usb2_data,
},
{
+ .compatible = "ti,omap5-usb2",
+ .data = &omap5_usb2_data,
+ },
+ {
.compatible = "ti,dra7x-usb2",
.data = &dra7x_usb2_data,
},
--
1.8.3.1
prev parent reply other threads:[~2014-03-06 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 12:41 [PATCH v2 0/3] phy-omap-usb2 driver enhancements George Cherian
2014-03-06 12:41 ` [PATCH v2 1/3] phy: omap-usb2: Adapt phy-omap-usb2 for AM437x George Cherian
2014-03-06 12:41 ` [PATCH v2 2/3] phy: omap-usb2: Provide workaround for USB2PHY false disconnect George Cherian
2014-03-06 12:41 ` George Cherian [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=1394109714-31228-4-git-send-email-george.cherian@ti.com \
--to=george.cherian@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kishon@ti.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=tony@atomide.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).