From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Doug Anderson <dianders@chromium.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Klaus Goger <klaus.goger@theobroma-systems.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: cpufreq(-dt) with two clocks but one regulator
Date: Tue, 19 Sep 2017 08:25:59 -0700 [thread overview]
Message-ID: <20170919152559.GA16005@ubuntu> (raw)
In-Reply-To: <2997079.BKPG7M6LVv@diego>
On 19-09-17, 11:19, Heiko Stübner wrote:
> Am Montag, 18. September 2017, 16:37:56 CEST schrieb Doug Anderson:
> > (Untested) Can't you change the opp table and use the fancier
> > operating point descriptions that give <target min max>?
And that's exactly what I was going to suggest :)
> funny, that I never noticed that opps are also specified for
> (target, min, max) values.
>
> Thanks for pointing me to the right direction and this seems to
> actually work. Although I noticed that obviously the max value
> needs to always be the global maximum (1125000 here) for both
> opp tables, to make the regulator framework happy.
Great.
--
viresh
prev parent reply other threads:[~2017-09-19 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 22:53 cpufreq(-dt) with two clocks but one regulator Heiko Stuebner
2017-09-18 1:24 ` Viresh Kumar
2017-09-18 22:40 ` Heiko Stuebner
2017-09-18 23:37 ` Doug Anderson
2017-09-19 9:19 ` Heiko Stübner
2017-09-19 15:25 ` Viresh Kumar [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=20170919152559.GA16005@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=klaus.goger@theobroma-systems.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=vincent.guittot@linaro.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.