[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9879b9c5-a5e6-425b-8184-868880f04f53@samsung.com>
Date: Thu, 17 Jun 2021 13:27:13 +0900
From: Chanwoo Choi <cw00.choi@...sung.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Hsin-Yi Wang <hsinyi@...omium.org>,
"Viresh Kumar )" <vireshk@...nel.org>, Nishanth Menon <nm@...com>,
Stephen Boyd <sboyd@...nel.org>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org,
"andrew-sh . cheng" <andrew-sh.cheng@...iatek.com>
Subject: Re: [PATCH] opp: of: Allow lazy-linking of required-opps to non
genpd
On 6/17/21 1:00 PM, Viresh Kumar wrote:
> On 17-06-21, 13:09, Chanwoo Choi wrote:
>> On 6/17/21 12:33 PM, Viresh Kumar wrote:
>>> On 17-06-21, 10:13, Chanwoo Choi wrote:
>>>> The devfreq driver(exynos-bus.c) has used the dev_pm_opp_set_rate()
>>>> and used the passive governor without the required-opp property.
>>>
>>> Which is fine.
>>>
>>>> I have a plan to use the required-opp property
>>>> between devfreq drivers (exynos-bus.c) with dev_pm_opp_set_rate().
>>>>
>>>> I'll support them on later if this approach doesn't break the any
>>>> rule of required-opp property.
>>>
>>> You will be required to make some changes in core for that I am
>>> afraid. It won't work automatically.
>>
>> Do you think that better to use clk_enable/regulator_enable directly
>> instead of dev_pm_opp_set_rate() for using required-opp property?
>
> No. All I am saying is that the OPP core won't work for your use case
> today and may need some updates.
OK. I'll update them for this case.
--
Best Regards,
Chanwoo Choi
Samsung Electronics
Powered by blists - more mailing lists