From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 06/12] usb: phy-mxs: change description of usb device speed
Date: Fri, 27 Dec 2013 10:38:35 +0800 [thread overview]
Message-ID: <1388111921-17326-7-git-send-email-peter.chen@freescale.com> (raw)
In-Reply-To: <1388111921-17326-1-git-send-email-peter.chen@freescale.com>
Change "high speed" to "HS"
Change "non-high speed" to "FS/LS"
Implementation of notify_suspend and notify_resume will be different
according to mxs_phy_data->flags.
Signed-off-by: Peter Chen <peter.chen@freescale.com>
---
drivers/usb/phy/phy-mxs-usb.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-usb.c
index 12671c5..c53b327 100644
--- a/drivers/usb/phy/phy-mxs-usb.c
+++ b/drivers/usb/phy/phy-mxs-usb.c
@@ -161,8 +161,8 @@ static int mxs_phy_suspend(struct usb_phy *x, int suspend)
static int mxs_phy_on_connect(struct usb_phy *phy,
enum usb_device_speed speed)
{
- dev_dbg(phy->dev, "%s speed device has connected\n",
- (speed == USB_SPEED_HIGH) ? "high" : "non-high");
+ dev_dbg(phy->dev, "%s device has connected\n",
+ (speed == USB_SPEED_HIGH) ? "HS" : "FS/LS");
if (speed == USB_SPEED_HIGH)
writel(BM_USBPHY_CTRL_ENHOSTDISCONDETECT,
@@ -174,8 +174,8 @@ static int mxs_phy_on_connect(struct usb_phy *phy,
static int mxs_phy_on_disconnect(struct usb_phy *phy,
enum usb_device_speed speed)
{
- dev_dbg(phy->dev, "%s speed device has disconnected\n",
- (speed == USB_SPEED_HIGH) ? "high" : "non-high");
+ dev_dbg(phy->dev, "%s device has disconnected\n",
+ (speed == USB_SPEED_HIGH) ? "HS" : "FS/LS");
if (speed == USB_SPEED_HIGH)
writel(BM_USBPHY_CTRL_ENHOSTDISCONDETECT,
--
1.7.8
next prev parent reply other threads:[~2013-12-27 2:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 2:38 [PATCH v9 00/12] Add power management support for mxs phy Peter Chen
2013-12-27 2:38 ` [PATCH v9 01/12] usb: doc: phy-mxs: Add more compatible strings Peter Chen
2014-02-18 16:49 ` Felipe Balbi
2014-02-19 1:12 ` Shawn Guo
2014-02-19 1:24 ` Felipe Balbi
2014-02-19 0:44 ` Peter Chen
2014-02-19 1:50 ` Shawn Guo
2013-12-27 2:38 ` [PATCH v9 02/12] usb: phy-mxs: Add platform judgement code Peter Chen
2013-12-27 2:38 ` [PATCH v9 03/12] usb: phy-mxs: Add auto clock and power setting Peter Chen
2013-12-27 2:38 ` [PATCH v9 04/12] usb: doc: phy-mxs: update binding for adding anatop phandle Peter Chen
2013-12-27 2:38 ` [PATCH v9 05/12] usb: phy-mxs: Add anatop regmap Peter Chen
2013-12-27 2:38 ` Peter Chen [this message]
2013-12-27 2:38 ` [PATCH v9 07/12] usb: phy-mxs: Enable IC fixes for related SoCs Peter Chen
2013-12-27 2:38 ` [PATCH v9 08/12] usb: phy-mxs: add controller id Peter Chen
2013-12-27 2:38 ` [PATCH v9 09/12] usb: phy: Add set_wakeup API Peter Chen
2013-12-27 2:38 ` [PATCH v9 10/12] usb: phy-mxs: Add implementation of set_wakeup Peter Chen
2013-12-27 2:38 ` [PATCH v9 11/12] usb: phy-mxs: Add system suspend/resume API Peter Chen
2014-02-18 16:50 ` Felipe Balbi
2014-02-19 0:54 ` Peter Chen
2013-12-27 2:38 ` [PATCH v9 12/12] usb: phy-mxs: Add sync time after controller clear phcd Peter Chen
2014-01-20 6:48 ` [PATCH v9 00/12] Add power management support for mxs phy Peter Chen
2014-02-07 5:48 ` Peter Chen
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=1388111921-17326-7-git-send-email-peter.chen@freescale.com \
--to=peter.chen@freescale.com \
--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;
as well as URLs for NNTP newsgroup(s).