From: Kevin Hilman <khilman@ti.com>
To: Afzal Mohammed <afzal@ti.com>, Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org, Sekhar Nori <nsekhar@ti.com>
Subject: Re: [PATCH] cpufreq: OMAP: specify range for voltage scaling
Date: Thu, 01 Mar 2012 14:07:51 -0800 [thread overview]
Message-ID: <87d38wf008.fsf@ti.com> (raw)
In-Reply-To: <87fwdshyhk.fsf@ti.com> (Kevin Hilman's message of "Thu, 01 Mar 2012 12:12:23 -0800")
+Tero
Kevin Hilman <khilman@ti.com> writes:
> Afzal Mohammed <afzal@ti.com> writes:
>
>> Specify voltage in ranges for regulator. Range
>> used is tolerance specified for OPP.
>>
>> This helps to achieve DVFS with a wider range of
>> regulators.
>>
>> Cc: Kevin Hilman <khilman@ti.com>
>> Cc: Sekhar Nori <nsekhar@ti.com>
>> Signed-off-by: Afzal Mohammed <afzal@ti.com>
>
> Thanks, will queue this with the CPUfreq changes for MPU DVFS.
Actually, not quite yet...
After some testing with the SMPS regulators, this won't quite work with
the current SMPS regulators. Does this actually work with the
regulators you're using?
For OMAPs using VC/VP for voltage scaling, the TWL regulator passes on
the voltage requested directly to the voltage layer. When using voltage
- tolerance, this results in voltages that the voltage layer doesn't
know about because they do not match any of the voltages from the known
OPPs.
The problem that we have is that while the regulators can support a
broad range of voltages (from min to max with a some step), the on-chip
voltage domains cannot, which is why we have defined the OPPs which are
known to work.
Tero, for the SMPS regulators, would it be possible to configure the
regulators so that only a discrete set voltages are availble to pick
from? These should be initialied from the OPP layer.
Somehow we need to support something like $SUBJECT patch in order to
support a broad range of regulators. The OMAP voltagedomain
limitations need to configured in platform specific way such that the
CPUfreq driver can remain generic.
Kevin
next prev parent reply other threads:[~2012-03-01 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 13:49 [PATCH] cpufreq: OMAP: specify range for voltage scaling Afzal Mohammed
2012-03-01 20:12 ` Kevin Hilman
2012-03-01 22:07 ` Kevin Hilman [this message]
2012-03-02 10:19 ` Tero Kristo
2012-03-02 22:39 ` Kevin Hilman
2012-03-02 10:56 ` Mohammed, Afzal
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=87d38wf008.fsf@ti.com \
--to=khilman@ti.com \
--cc=afzal@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=t-kristo@ti.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;
as well as URLs for NNTP newsgroup(s).