Re: [PATCH v3 1/3] cpufreq: add cpufreq_driver_resolve_freq()
From: Viresh Kumar
Date: Fri Jul 22 2016 - 11:16:48 EST
On 21-07-16, 17:44, Steve Muckle wrote:
> Going back and checking I see I was thinking of your suggestion that
> cpufreq_register_driver() check that only target() drivers offer a
> resolve_freq() callback. I put a comment for this in cpufreq.h but not a
> check - I could add a check in another patch if you like.
That can be done as we aren't supporting the ->resolve_freq() callback
for ->target_index() drivers.
> Long term as I was mentioning in the other thread I think it'd be good
> if the current target() drivers were modified to supply resolve_freq(),
> and that cpufreq_register_driver() were again changed to require it for
> those drivers.
There is no need for us to force this, its really optional for such
platforms. Worst case, schedutil wouldn't work at the best, so what?
Its a platform driver's choice, isn't it ?