On Thu, May 15, 2014 at 11:07 AM, Viresh Kumar <viresh.ku...@linaro.org> wrote: > On 15 May 2014 11:00, Inderpal Singh <inderpa...@samsung.com> wrote: >> On Thu, May 15, 2014 at 10:34 AM, Viresh Kumar <viresh.ku...@linaro.org> >> wrote: >>> On 15 May 2014 10:22, Inderpal Singh <inderpa...@samsung.com> wrote: >>> >>>> What i am saying that "what if we are not going to re-use again ? " >>> >>> That's what I said: >>> >>> Yes, it will keep occupying some space but there is only one instance >>> of that per 'cluster' and is very much affordable instead of building it >>> again.. >>> >>> So, we may not need to free it. >> >> Its not just about cpufreq. There may be others using OPPs as well. >> For example devfreq. > > And who is stopping these to use the already built ones? Exactly for > this reason I have been saying that lets not free OPPs already built. > Devfreq can simply use the ones built by cpufreq, even if cpufreq isn't > using it anymore.
I think I did not make myself clear. Devfreq will have its own opp table associated with its own device. It does not uses the opp table of cpus. Hence there may be need to free the table if driver (at least devfreq) getting un-registered. > -- > To unsubscribe from this list: send the line "unsubscribe linux-pm" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/