From: David Brownell <david-b@pacbell.net>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [patch 2.6.28-rc3-omap 0/4] twl4030 regulator support
Date: Thu, 13 Nov 2008 17:25:05 -0800 [thread overview]
Message-ID: <200811131725.05573.david-b@pacbell.net> (raw)
In-Reply-To: <20081114010311.GE3106@atomide.com>
On Thursday 13 November 2008, Tony Lindgren wrote:
>
> > Oh, and somewhat related ... nothing seems to turn off unused
> > regulators. I'm thinking that bitmasks to define the P1/P2/P3
> > group memberships of most power resources would do the job.
>
> Yeah I was wondering about that too. Should the processor group
> membership be set only once during init?
I think it should certainly be set during init. The PM scripts
don't change membership, but I can imagine some of them would
want to use custom type or subtype codes that would also need to
be set during init.
The current way to enable/disable a regulator for Linux purposes
is to add/remove it from the P1 group. That seems OK for now...
only a handful of regulators use software control like that,
which would change membership after init.
But we *could* enable/disable by directly setting the mode.
I decided against doing it that way, on the grounds that until
we get some use cases that need something else, we're best off
keeping things simple.
- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-11-14 1:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 1:56 [patch 2.6.28-rc3-omap 0/4] twl4030 regulator support David Brownell
2008-11-13 22:32 ` Tony Lindgren
2008-11-14 0:16 ` David Brownell
2008-11-14 0:46 ` David Brownell
2008-11-14 1:03 ` Tony Lindgren
2008-11-14 1:25 ` David Brownell [this message]
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=200811131725.05573.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.