From: Bobby Crabtree <bobbyc@codeaurora.org>
To: broonie@opensource.wolfsonmicro.com, lrg@slimlogic.co.uk
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: regulator voltage aggregation
Date: Tue, 17 Aug 2010 11:06:10 -0700 [thread overview]
Message-ID: <4C6ACF92.7050506@codeaurora.org> (raw)
I'm looking to upstream a new feature in which the regulator core
aggregates voltage requests from multiple consumers and applies the best
fitting voltage (e.g. max voltage) to a shared supply. The core would
recompute the best fitting voltage when a consumer requests a voltage
change or requests to enable/disable the regulator (similar logic to
DRMS).
The reason we need this feature is for power savings. It would allow two
or more consumers to "vote" on a voltage that's lower than the normal
operating voltage.
I've got a couple implementations in mind.
1. Introduce a new API:
int regulator_set_optimum_voltage(struct regulator *regulator,
int min_uV, int max_uV);
2. Add a flag to the regulation_constraints structure and reuse the
existing regulator_set_voltage API.
struct regulation_constraints {
...
unsigned aggregate_uV:1;
...
};
Does this sound like a reasonable feature? And if so, are there any
preferences as to how the feature is implemented and exposed?
Bobby Crabtree
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next reply other threads:[~2010-08-17 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 18:06 Bobby Crabtree [this message]
2010-08-17 18:15 ` regulator voltage aggregation Mark Brown
2010-08-17 19:33 ` Bobby Crabtree
2010-08-17 19:50 ` Mark Brown
2010-08-17 20:44 ` Bobby Crabtree
2010-08-17 21:03 ` Mark Brown
2010-08-17 18:28 ` Alan Cox
2010-08-17 18:22 ` Mark Brown
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=4C6ACF92.7050506@codeaurora.org \
--to=bobbyc@codeaurora.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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