[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161025190114.GV26139@codeaurora.org>
Date: Tue, 25 Oct 2016 12:01:14 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Rafael Wysocki <rjw@...ysocki.net>, nm@...com,
Viresh Kumar <vireshk@...nel.org>,
linaro-kernel@...ts.linaro.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>, robh@...nel.org,
d-gerlach@...com, broonie@...nel.org
Subject: Re: [PATCH V2 7/8] PM / OPP: Allow platform specific custom
opp_set_rate() callbacks
On 10/20, Viresh Kumar wrote:
> The generic opp_set_rate() handler isn't sufficient for platforms with
> complex DVFS. For example, some TI platforms have multiple regulators
> for a CPU device. The order in which various supplies need to be
> programmed is only known to the platform code and its best to leave it
> to it.
>
> This patch implements APIs to register platform specific opp_set_rate()
> callback.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> ---
Overall it looks ok, but I'd prefer set_opp instead of set_rate.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Powered by blists - more mailing lists