[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b634343a-8005-fc35-e38b-bfeaa7310a70@gmail.com>
Date: Fri, 22 Jan 2021 00:41:46 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Viresh Kumar <viresh.kumar@...aro.org>,
Viresh Kumar <vireshk@...nel.org>, Nishanth Menon <nm@...com>,
Stephen Boyd <sboyd@...nel.org>
Cc: linux-pm@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
Rafael Wysocki <rjw@...ysocki.net>,
Sibi Sankar <sibis@...eaurora.org>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 03/13] opp: Keep track of currently programmed OPP
21.01.2021 14:17, Viresh Kumar пишет:
> @@ -1074,15 +1091,18 @@ int dev_pm_opp_set_rate(struct device *dev, unsigned long target_freq)
>
> if (!ret) {
> ret = _set_opp_bw(opp_table, opp, dev, false);
> - if (!ret)
> + if (!ret) {
> opp_table->enabled = true;
> + dev_pm_opp_put(old_opp);
> +
> + /* Make sure current_opp doesn't get freed */
> + dev_pm_opp_get(opp);
> + opp_table->current_opp = opp;
> + }
> }
I'm a bit surprised that _set_opp_bw() isn't used similarly to
_set_opp_voltage() in _generic_set_opp_regulator().
I'd expect the BW requirement to be raised before the clock rate goes UP.
Powered by blists - more mailing lists