From: Kishon Vijay Abraham I <kishon@ti.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@ti.com>,
Vivek Gautam <gautam.vivek@samsung.com>,
<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 3/6] arm: omap3: twl: use the new lookup method with usb phy
Date: Thu, 11 Sep 2014 20:56:15 +0530 [thread overview]
Message-ID: <5411BF17.1060909@ti.com> (raw)
In-Reply-To: <1408620803-10464-4-git-send-email-heikki.krogerus@linux.intel.com>
Hi,
On Thursday 21 August 2014 05:03 PM, Heikki Krogerus wrote:
> Provide complete association for the phy and it's user
> (musb) with the new phy lookup method.
>
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> arch/arm/mach-omap2/twl-common.c | 18 ++++++++----------
> 1 file changed, 8 insertions(+), 10 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/twl-common.c b/arch/arm/mach-omap2/twl-common.c
> index b0d54da..b78383c 100644
> --- a/arch/arm/mach-omap2/twl-common.c
> +++ b/arch/arm/mach-omap2/twl-common.c
> @@ -91,18 +91,14 @@ void __init omap_pmic_late_init(void)
> }
>
> #if defined(CONFIG_ARCH_OMAP3)
> -struct phy_consumer consumers[] = {
> - PHY_CONSUMER("musb-hdrc.0", "usb"),
> -};
> -
> -struct phy_init_data init_data = {
> - .consumers = consumers,
> - .num_consumers = ARRAY_SIZE(consumers),
> +static struct phy_lookup twl4030_usb_lookup = {
> + .phy_name = "phy-twl4030_usb.0",
> + .dev_id = "musb-hdrc.0",
> + .con_id = "usb",
> };
Can use PHY_LOOKUP no?
Thanks
Kishon
next prev parent reply other threads:[~2014-09-11 15:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 11:33 [PATCHv3 0/6] phy: simplified phy lookup Heikki Krogerus
2014-08-21 11:33 ` [PATCH 1/6] phy: safer to_phy() macro Heikki Krogerus
2014-08-21 11:33 ` [PATCH 2/6] phy: improved lookup method Heikki Krogerus
2014-09-11 15:33 ` Kishon Vijay Abraham I
2014-09-12 14:07 ` Heikki Krogerus
2014-09-12 14:46 ` Kishon Vijay Abraham I
2014-09-15 12:35 ` Heikki Krogerus
2014-09-18 10:25 ` Heikki Krogerus
2014-09-22 11:37 ` Kishon Vijay Abraham I
2014-09-23 10:53 ` Heikki Krogerus
2014-09-23 11:03 ` Kishon Vijay Abraham I
2014-09-23 11:43 ` Heikki Krogerus
2014-09-24 9:44 ` Kishon Vijay Abraham I
2014-09-25 7:00 ` Heikki Krogerus
2014-09-29 6:28 ` Kishon Vijay Abraham I
2014-08-21 11:33 ` [PATCH 3/6] arm: omap3: twl: use the new lookup method with usb phy Heikki Krogerus
2014-09-11 15:26 ` Kishon Vijay Abraham I [this message]
2014-09-12 13:50 ` Heikki Krogerus
2014-08-21 11:33 ` [PATCH 4/6] phy: remove the old lookup method Heikki Krogerus
2014-08-25 7:41 ` Vivek Gautam
2014-08-25 8:17 ` Heikki Krogerus
2014-08-25 8:25 ` Vivek Gautam
2014-08-26 8:27 ` [PATCHv4 " Heikki Krogerus
2014-08-21 11:33 ` [PATCH 5/6] base: platform: name the device already during allocation Heikki Krogerus
2014-08-21 11:33 ` [PATCH 6/6] usb: dwc3: host: convey the PHYs to xhci Heikki Krogerus
2014-09-11 15:01 ` Kishon Vijay Abraham I
2014-09-12 13:49 ` Heikki Krogerus
2014-09-12 14:11 ` Kishon Vijay Abraham I
2014-09-15 12:06 ` Heikki Krogerus
2014-09-16 6:37 ` Kishon Vijay Abraham I
2014-09-16 12:13 ` Heikki Krogerus
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=5411BF17.1060909@ti.com \
--to=kishon@ti.com \
--cc=balbi@ti.com \
--cc=gautam.vivek@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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).