linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 08/15] usb: phy-mxs: add controller id
Date: Thu, 20 Feb 2014 13:14:37 +0800	[thread overview]
Message-ID: <1392873284-9386-9-git-send-email-peter.chen@freescale.com> (raw)
In-Reply-To: <1392873284-9386-1-git-send-email-peter.chen@freescale.com>

It is used to access un-regulator registers according to
different controllers.

Signed-off-by: Peter Chen <peter.chen@freescale.com>
---
 drivers/usb/phy/phy-mxs-usb.c |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-usb.c
index cb71135..3009ab5 100644
--- a/drivers/usb/phy/phy-mxs-usb.c
+++ b/drivers/usb/phy/phy-mxs-usb.c
@@ -106,6 +106,7 @@ struct mxs_phy {
 	struct clk *clk;
 	const struct mxs_phy_data *data;
 	struct regmap *regmap_anatop;
+	int port_id;
 };
 
 static int mxs_phy_hw_init(struct mxs_phy *mxs_phy)
@@ -250,6 +251,11 @@ static int mxs_phy_probe(struct platform_device *pdev)
 		}
 	}
 
+	ret = of_alias_get_id(np, "usbphy");
+	if (ret < 0)
+		dev_dbg(&pdev->dev, "failed to get alias id, errno %d\n", ret);
+	mxs_phy->port_id = ret;
+
 	mxs_phy->phy.io_priv		= base;
 	mxs_phy->phy.dev		= &pdev->dev;
 	mxs_phy->phy.label		= DRIVER_NAME;
-- 
1.7.8

  parent reply	other threads:[~2014-02-20  5:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20  5:14 [PATCH v10 00/15] Add power management support for mxs phy Peter Chen
2014-02-20  5:14 ` [PATCH v10 01/15] usb: doc: phy-mxs: Add more compatible strings Peter Chen
2014-02-21  9:13   ` Mark Rutland
2014-02-21  9:40     ` Peter Chen
2014-02-21  9:46       ` Marc Kleine-Budde
2014-02-21  9:05         ` Peter Chen
2014-02-21 12:38       ` Mark Rutland
2014-02-20  5:14 ` [PATCH v10 02/15] usb: phy-mxs: Add platform judgement code Peter Chen
2014-02-20  5:14 ` [PATCH v10 03/15] usb: phy-mxs: Add auto clock and power setting Peter Chen
2014-02-20  5:14 ` [PATCH v10 04/15] usb: doc: phy-mxs: update binding for adding anatop phandle Peter Chen
2014-02-21  9:14   ` Mark Rutland
2014-02-21  8:57     ` Peter Chen
2014-02-20  5:14 ` [PATCH v10 05/15] usb: phy-mxs: Add anatop regmap Peter Chen
2014-02-20  5:14 ` [PATCH v10 06/15] usb: phy-mxs: change description of usb device speed Peter Chen
2014-02-20  5:14 ` [PATCH v10 07/15] usb: phy-mxs: Enable IC fixes for related SoCs Peter Chen
2014-02-20  5:14 ` Peter Chen [this message]
2014-02-20  5:14 ` [PATCH v10 09/15] usb: phy: Add set_wakeup API Peter Chen
2014-02-20  5:14 ` [PATCH v10 10/15] usb: phy-mxs: Add implementation of set_wakeup Peter Chen
2014-02-21  9:21   ` Mark Rutland
2014-02-21  9:03     ` Peter Chen
2014-02-20  5:14 ` [PATCH v10 11/15] usb: phy-mxs: Add system suspend/resume API Peter Chen
2014-02-20  5:14 ` [PATCH v10 12/15] usb: phy-mxs: Add sync time after controller clear phcd Peter Chen
2014-02-20  5:14 ` [PATCH v10 13/15] ARM: dts: mxs: add mxs phy controller id Peter Chen
2014-02-20  5:14 ` [PATCH v10 14/15] ARM: dts: imx6: add anatop phandle for usbphy Peter Chen
2014-02-20  5:14 ` [PATCH v10 15/15] ARM: dts: imx6: add mxs phy controller id 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=1392873284-9386-9-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).