[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190617042654.xdqx5naxo3lq7kv6@vireshk-i7>
Date: Mon, 17 Jun 2019 09:56:54 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Rajendra Nayak <rnayak@...eaurora.org>
Cc: linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-pm@...r.kernel.org, linux-serial@...r.kernel.org,
linux-spi@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-scsi@...r.kernel.org, swboyd@...omium.org,
ulf.hansson@...aro.org, dianders@...omium.org, rafael@...nel.org
Subject: Re: [RFC v2 00/11] DVFS in the OPP core
On 20-03-19, 15:19, Rajendra Nayak wrote:
> This is a v2 of the RFC posted earlier by Stephen Boyd [1]
>
> As part of v2 I still follow the same approach of dev_pm_opp_set_rate()
> API using clk framework to round the frequency passed and making it
> accept 0 as a valid frequency indicating the frequency isn't required
> anymore. It just has a few more drivers converted to use this approach
> like dsi/dpu and ufs.
> ufs demonstrates the case of having to handle multiple power domains, one
> of which is scalable.
>
> The patches are based on 5.1-rc1 and depend on some ufs fixes I posted
> earlier [2] and a DT patch to include the rpmpd header [3]
>
> [1] https://lkml.org/lkml/2019/1/28/2086
> [2] https://lkml.org/lkml/2019/3/8/70
> [3] https://lkml.org/lkml/2019/3/20/120
>
> Rajendra Nayak (10):
> OPP: Make dev_pm_opp_set_rate() with freq=0 as valid
>
> Stephen Boyd (1):
> OPP: Don't overwrite rounded clk rate
I have applied modified version of these two patches to the OPP tree now.
Thanks.
--
viresh
Powered by blists - more mailing lists