Messages in this thread | | | Date | Wed, 19 Mar 2014 10:33:59 +0530 | Subject | Re: [PATCH 0/2] Add exit_prepare callback to the cpufreq_driver interface. | From | Viresh Kumar <> |
| |
On 18 March 2014 17:46, Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> wrote: > Agreed. As far as I understand, for ->target drivers, today we use GOV_STOP > to stop managing the CPU going offline. And for ->setpolicy drivers, we will > use this new callback to achieve the same goal.
So a better question would be: What's the purpose of ->stop() call for a policy? Stop managing CPUs of that policy? Or even do something on CPUs of a policy before CPUs are offlined?
Probably in the current solution Dirk is doing both these things..
And so I thought maybe its better not to restrict ->stop() to just setpolicy() drivers.
| |