From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: kalle.jokiniemi@nokia.com
Cc: lrg@slimlogic.co.uk, mchehab@infradead.org, svarbatov@mm-sol.com,
saaguirre@ti.com, grosikopulos@mm-sol.com,
vimarsh.zutshi@nokia.com, Sakari.Ailus@nokia.com,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [RFC] Regulator state after regulator_get
Date: Thu, 28 Apr 2011 12:14:48 +0100 [thread overview]
Message-ID: <20110428111447.GA19484@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <9D0D31AA57AAF5499AFDC63D6472631B09C858@008-AM1MPN1-036.mgdnok.nokia.com>
On Thu, Apr 28, 2011 at 11:08:08AM +0000, kalle.jokiniemi@nokia.com wrote:
> I don't have a full set of regulators described, that's why things broke when
> I tried the regulator_full_constraints call earlier. But I don't think it would be too
> big issue to check the current after boot configuration and define all the
> regulators as you suggest. I will try this approach.
As I said in my previous mail if you've got a reagulator you don't know
about which is on you can give it an always_on constraint until you
figure out what (if anything) should be controlling it.
next prev parent reply other threads:[~2011-04-28 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 9:01 [RFC] Regulator state after regulator_get kalle.jokiniemi
2011-04-28 9:34 ` Sakari Ailus
2011-04-28 9:44 ` kalle.jokiniemi
2011-04-28 10:20 ` Mark Brown
2011-04-28 10:27 ` Sakari Ailus
2011-04-28 10:40 ` Mark Brown
2011-04-28 11:07 ` Sakari Ailus
2011-04-28 10:06 ` Mark Brown
2011-04-28 11:08 ` kalle.jokiniemi
2011-04-28 11:14 ` Mark Brown [this message]
2011-04-28 11:58 ` kalle.jokiniemi
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=20110428111447.GA19484@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Sakari.Ailus@nokia.com \
--cc=grosikopulos@mm-sol.com \
--cc=kalle.jokiniemi@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=mchehab@infradead.org \
--cc=saaguirre@ti.com \
--cc=svarbatov@mm-sol.com \
--cc=vimarsh.zutshi@nokia.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