[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohponTH9X6AUX_0TJbRw0bUw5WQaE6oeDpGW9avTLifLGBCQ@mail.gmail.com>
Date: Thu, 15 May 2014 11:07:33 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Inderpal Singh <inderpal.s@...sung.com>
Cc: Nishanth Menon <nm@...com>, Pavel Machek <pavel@....cz>,
"[Chander Kashyap" <chander.kashyap@...aro.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"Brown, Len" <len.brown@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Chander Kashyap <k.chander@...sung.com>
Subject: Re: [PATCH] PM / OPP: discard duplicate OPP additions
On 15 May 2014 11:00, Inderpal Singh <inderpal.s@...sung.com> wrote:
> On Thu, May 15, 2014 at 10:34 AM, Viresh Kumar <viresh.kumar@...aro.org> wrote:
>> On 15 May 2014 10:22, Inderpal Singh <inderpal.s@...sung.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists