From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Anirudh Ghayal <aghayal@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
collinsd@codeaurora.org, khilman@ti.com, tsoni@codeaurora.org
Subject: Re: Shared regulator usage
Date: Tue, 27 Nov 2012 11:32:21 +0000 [thread overview]
Message-ID: <20121127113221.GB4468@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50B4A0D1.7010707@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
On Tue, Nov 27, 2012 at 04:45:29PM +0530, Anirudh Ghayal wrote:
> At 1.4Ghz the cpu-freq driver votes for 1.3v, then the CPR kicks in
> and recommends a voltage of 1.275v. Now a set_voltage with this new
> level (1.275v, 1.275) fails as it does not satisfy the limits of
> the cpu-freq driver. It is not possible to tweak this range any
> further as it would not achieve the goal of micro-adjusting the
> voltage to save power.
> Such scenarios are very likely to occur in the future on embedded
> systems where there is a need to conserve power by introducing some
> adaptive voltage scaling techniques based on various parameters such
> as temperature/sensitivity.
This just sounds like bad software design. You've got two unrelated
drivers setting the same thing without talking to each other even though
the one is trying to adjust the voltage set by the other without
actually knowing the voltage that the other one set. Why are these
separate drivers?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-27 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 13:13 Shared regulator usage aghayal
2012-11-26 13:47 ` Mark Brown
2012-11-27 11:15 ` Anirudh Ghayal
2012-11-27 11:32 ` Mark Brown [this message]
2012-11-27 15:17 ` Kevin Hilman
2012-11-27 15:17 ` Kevin Hilman
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=20121127113221.GB4468@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=aghayal@codeaurora.org \
--cc=collinsd@codeaurora.org \
--cc=khilman@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tsoni@codeaurora.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 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.