From: Greg KH <greg@kroah.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Waldemar Rymarkiewicz <waldemar.rymarkiewicz@gmail.com>,
"4 . 6+" <stable@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4.9] PM / OPP: Update voltage in case freq == old_freq
Date: Tue, 10 Jul 2018 15:59:12 +0200 [thread overview]
Message-ID: <20180710135912.GI1123@kroah.com> (raw)
In-Reply-To: <3717ee50c1f1f48cffcb1a2e41c04e28881776d1.1530521347.git.viresh.kumar@linaro.org>
On Mon, Jul 02, 2018 at 02:19:47PM +0530, Viresh Kumar wrote:
> From: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@gmail.com>
>
> Original commit c5c2a97b3ac7 ("PM / OPP: Update voltage in case freq ==
> old_freq").
>
> This commit fixes a rare but possible case when the clk rate is updated
> without update of the regulator voltage.
>
> At boot up, CPUfreq checks if the system is running at the right freq. This
> is a sanity check in case a bootloader set clk rate that is outside of freq
> table present with cpufreq core. In such cases system can be unstable so
> better to change it to a freq that is preset in freq-table.
>
> The CPUfreq takes next freq that is >= policy->cur and this is our
> target_freq that needs to be set now.
>
> dev_pm_opp_set_rate(dev, target_freq) checks the target_freq and the
> old_freq (a current rate). If these are equal it returns early. If not,
> it searches for OPP (old_opp) that fits best to old_freq (not listed in
> the table) and updates old_freq (!).
>
> Here, we can end up with old_freq = old_opp.rate = target_freq, which
> is not handled in _generic_set_opp_regulator(). It's supposed to update
> voltage only when freq > old_freq || freq > old_freq.
>
> if (freq > old_freq) {
> ret = _set_opp_voltage(dev, reg, new_supply);
> [...]
> if (freq < old_freq) {
> ret = _set_opp_voltage(dev, reg, new_supply);
> if (ret)
>
> It results in, no voltage update while clk rate is updated.
>
> Example:
> freq-table = {
> 1000MHz 1.15V
> 666MHZ 1.10V
> 333MHz 1.05V
> }
> boot-up-freq = 800MHz # not listed in freq-table
> freq = target_freq = 1GHz
> old_freq = 800Mhz
> old_opp = _find_freq_ceil(opp_table, &old_freq); #(old_freq is modified!)
> old_freq = 1GHz
>
> Fixes: 6a0712f6f199 ("PM / OPP: Add dev_pm_opp_set_rate()")
> Cc: 4.6+ <stable@vger.kernel.org> # v4.6+
> Signed-off-by: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@gmail.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> Sending it for stable kernels from 4.6 until 4.9.
Always give me a hint as to what the original commit is, otherwise I
have to go dig for it :(
greg k-h
next prev parent reply other threads:[~2018-07-10 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 8:49 [PATCH v4.9] PM / OPP: Update voltage in case freq == old_freq Viresh Kumar
2018-07-10 13:59 ` Greg KH [this message]
2018-07-16 4:03 ` Viresh Kumar
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=20180710135912.GI1123@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
--cc=waldemar.rymarkiewicz@gmail.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).