public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Gupta, Ajay Kumar" <ajay.gupta@ti.com>
Cc: "felipe.balbi@nokia.com" <felipe.balbi@nokia.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Gadiyar, Anand" <gadiyar@ti.com>,
	"Aggarwal, Anuj" <anuj.aggarwal@ti.com>
Subject: Re: Query: Regulator framework in EHCI driver
Date: Wed, 4 Nov 2009 13:39:23 +0000	[thread overview]
Message-ID: <20091104133922.GD25044@sirena.org.uk> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E73940436F9375B@dbde02.ent.ti.com>

On Wed, Nov 04, 2009 at 06:02:48PM +0530, Gupta, Ajay Kumar wrote:

> > You should be able to regulator_get() the 1v8 supply and
> > regulator_enable() it. The regulator was already setup in twl4030-core.c
> > so that should work just fine. 

> I can do regulator_get() and regulator_enable() but where ? Are you referring to board file?

> I was thinking of doing it in a generic form within EHCI driver (ehci-omap.c).

Do it in the EHCI driver.  The EHCI driver should just unconditionally
use the regulators, the regulator API will be compiled out if support is
disabled in Kconfig.

  reply	other threads:[~2009-11-04 13:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 11:55 Query: Regulator framework in EHCI driver Gupta, Ajay Kumar
2009-11-03 15:30 ` Felipe Balbi
2009-11-04 12:32   ` Gupta, Ajay Kumar
2009-11-04 13:39     ` Mark Brown [this message]
2009-11-04 14:30       ` Gadiyar, Anand
2009-11-04 14:41         ` Mark Brown
2009-11-04 14:45           ` Gadiyar, Anand
2009-11-04 14:48             ` Mark Brown
2009-11-04 14:50               ` Gadiyar, Anand
2009-11-04 14:56                 ` Mark Brown
2009-11-05  3:24                 ` Gupta, Ajay Kumar
2009-11-05  9:36                   ` Mark Brown
2009-11-05  9:41                     ` Felipe Balbi
2009-11-05 10:31                       ` Gadiyar, Anand
2009-11-05 11:19                         ` Mark Brown
2009-11-05 11:25                           ` Gadiyar, Anand
2009-11-11 14:56                             ` Gupta, Ajay Kumar
2009-11-11 15:46                               ` Mark Brown
2009-11-12  3:41                                 ` Gupta, Ajay Kumar
2009-11-12  3:51                                   ` Gupta, Ajay Kumar
2009-11-12  6:21                                   ` Gadiyar, Anand
2009-11-12  6:48                                     ` Gupta, Ajay Kumar
2009-11-12 12:16                                   ` Mark Brown
2009-11-13  4:22                                     ` Gupta, Ajay Kumar
2009-11-13 12:55                                       ` Mark Brown
2009-11-15  7:29                                         ` Gupta, Ajay Kumar

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=20091104133922.GD25044@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ajay.gupta@ti.com \
    --cc=anuj.aggarwal@ti.com \
    --cc=felipe.balbi@nokia.com \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@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