From: Felipe Balbi <balbi@ti.com>
To: Shubhrajyoti <shubhrajyoti@ti.com>
Cc: Ajay Kumar Gupta <ajay.gupta@ti.com>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
balbi@ti.com, tony@atomide.com, Ravi Babu <ravibabu@ti.com>
Subject: Re: [PATCH 1/3 v5] usb: musb: Add support for ti81xx platform
Date: Thu, 9 Feb 2012 10:08:23 +0200 [thread overview]
Message-ID: <20120209080822.GR1121@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <4F321320.8010709@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
On Wed, Feb 08, 2012 at 11:46:00AM +0530, Shubhrajyoti wrote:
> On Wednesday 08 February 2012 09:56 AM, Ajay Kumar Gupta wrote:
> > +static int dsps_musb_init(struct musb *musb)
> > +{
> > + struct device *dev = musb->controller;
> > + struct musb_hdrc_platform_data *plat = dev->platform_data;
> > + struct platform_device *pdev = to_platform_device(dev->parent);
> > + struct dsps_glue *glue = platform_get_drvdata(pdev);
> > + const struct dsps_musb_wrapper *wrp = glue->wrp;
> > + struct omap_musb_board_data *data = plat->board_data;
> > + void __iomem *reg_base = musb->ctrl_base;
> > + u32 rev, val;
> > + int status;
> > +
> > + /* mentor core register starts at offset of 0x400 from musb base */
> > + musb->mregs += wrp->musb_core_offset;
> > +
> > + /* NOP driver needs change if supporting dual instance */
> > + usb_nop_xceiv_register();
> > + musb->xceiv = otg_get_transceiver();
> > + if (!musb->xceiv)
> > + return -ENODEV;
> > +
> > + status = pm_runtime_get_sync(dev);
> > + if (status < 0) {
> > + dev_err(dev, "pm_runtime_get_sync FAILED");
> > + goto err0;
> > + }
> So you are doing a get_sync at init and you cut the clocks at exit only.
> Any particular reason for that.
that's a very good question. We're just adding a brand new file, which
is clean and stuff... so we might as well start with good PM
capabilities.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-09 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 4:26 [PATCH 1/3 v5] usb: musb: Add support for ti81xx platform Ajay Kumar Gupta
2012-02-08 4:26 ` [PATCH 2/3 v5] arm: omap: am335x: enable phy controls Ajay Kumar Gupta
[not found] ` <1328675212-29693-2-git-send-email-ajay.gupta-l0cyMroinI0@public.gmane.org>
2012-02-10 18:31 ` Tony Lindgren
[not found] ` <20120210183143.GS1426-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2012-02-13 4:26 ` Gupta, Ajay Kumar
2012-02-13 6:49 ` Felipe Balbi
2012-02-13 9:40 ` Gupta, Ajay Kumar
2012-02-13 10:11 ` Felipe Balbi
2012-02-08 4:26 ` [PATCH 3/3 v5] usb: musb: enable support for am335x Ajay Kumar Gupta
[not found] ` <1328675212-29693-1-git-send-email-ajay.gupta-l0cyMroinI0@public.gmane.org>
2012-02-08 6:16 ` [PATCH 1/3 v5] usb: musb: Add support for ti81xx platform Shubhrajyoti
2012-02-09 8:08 ` Felipe Balbi [this message]
2012-02-09 11:30 ` Gupta, Ajay Kumar
[not found] ` <47CEF8C4B26E8C44B22B028A650E0EA9317F03C8-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-02-13 7:05 ` Gupta, Ajay Kumar
-- strict thread matches above, loose matches on Subject: below --
2012-02-08 7:41 Ajay Kumar Gupta
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=20120209080822.GR1121@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=ajay.gupta@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ravibabu@ti.com \
--cc=shubhrajyoti@ti.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).