From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: "Gupta, Ajay Kumar" <ajay.gupta@ti.com>,
"felipe.balbi@nokia.com" <felipe.balbi@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Aggarwal, Anuj" <anuj.aggarwal@ti.com>
Subject: Re: Query: Regulator framework in EHCI driver
Date: Wed, 4 Nov 2009 14:56:26 +0000 [thread overview]
Message-ID: <20091104145626.GC30644@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB030A67DE8A@dbde02.ent.ti.com>
On Wed, Nov 04, 2009 at 08:20:46PM +0530, Gadiyar, Anand wrote:
> I meant: for the same driver (say EHCI in this case) on two different
> boards, if one of them needs a particular regulator (say the 1v8 from TWL4030)
> and the other needs none at all (but needs the regulator API in general for
> other devices on the board), then what would happen?
Like I say, if the kernel is built with regulator support then a fixed
voltage regulator should be defined representing the supply if it is
provided by a fixed voltage regulator - if the supply is essential to
the correct operation of the device this will reflect the actual
hardware.
If the supply is genuinely optional and need not be connected for
correct operation of the device then the consumer driver should
gracefully handle failure to acquire the regulator, for example by
disabling functionality that depends on the additional supply, but this
is relatively unusual.
next prev parent reply other threads:[~2009-11-04 14:56 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
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 [this message]
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=20091104145626.GC30644@rakim.wolfsonmicro.main \
--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