From: George Cherian <george.cherian@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org
Cc: balbi@ti.com, rogerq@ti.com
Subject: Re: [PATCH v3] phy: omap-control: update dra7 and am437 usb2 bindings
Date: Fri, 7 Mar 2014 11:37:57 +0530 [thread overview]
Message-ID: <5319623D.5030909@ti.com> (raw)
In-Reply-To: <1394171280-13359-1-git-send-email-kishon@ti.com>
On 3/7/2014 11:18 AM, Kishon Vijay Abraham I wrote:
> From: Roger Quadros <rogerq@ti.com>
>
> The dra7-usb2 and am437-usb2 bindings have not yet been used.
> Change them to be more elegant.
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> ---
> Changes from v2:
> Kept only the drivers/phy part in this patch
>
> drivers/phy/phy-omap-control.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/phy/phy-omap-control.c b/drivers/phy/phy-omap-control.c
> index 17fc200..a7e2d7f 100644
> --- a/drivers/phy/phy-omap-control.c
> +++ b/drivers/phy/phy-omap-control.c
> @@ -228,11 +228,11 @@ static const struct of_device_id omap_control_phy_id_table[] = {
> .data = &pipe3_data,
> },
> {
> - .compatible = "ti,control-phy-dra7usb2",
> + .compatible = "ti,control-phy-dra7-usb2",
> .data = &dra7usb2_data,
> },
> {
> - .compatible = "ti,control-phy-am437usb2",
> + .compatible = "ti,control-phy-am437-usb2",
Tony suggested to keep the compatible
ti,control-phy-usb2-dra7 and ti,control-phy-usb2-am437
http://www.spinics.net/lists/linux-omap/msg104040.html
Since we already have a ti,control-phy-usb2 I think it make sense to keep the new comaptible for dra7 and am437 as above.
> .data = &am437usb2_data,
> },
> {},
--
-George
prev parent reply other threads:[~2014-03-07 6:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 5:48 [PATCH v3] phy: omap-control: update dra7 and am437 usb2 bindings Kishon Vijay Abraham I
2014-03-07 6:07 ` 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=5319623D.5030909@ti.com \
--to=george.cherian@ti.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rogerq@ti.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).