[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpomN=e2ygpv_y+PXaPQM_7ULkQoKa0UrU5CN9Yeqtp3v_g@mail.gmail.com>
Date: Mon, 26 May 2014 09:34:24 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Pavel Machek <pavel@....cz>
Cc: Eduardo Valentin <edubezval@...il.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arvind Chauhan <arvind.chauhan@....com>,
Ips Gandhi <inderpal.s@...sung.com>,
Nishanth Menon <nm@...com>,
Chander Kashyap <chander.kashyap@...aro.org>,
"Brown, Len" <len.brown@...el.com>,
Sudeep Holla <sudeep.holla@....com>
Subject: Re: [PATCH V3 1/8] cpufreq: cpufreq-cpu0: remove dependency on thermal
On 24 May 2014 18:29, Pavel Machek <pavel@....cz> wrote:
> On Fri 2014-05-23 10:03:27, Viresh Kumar wrote:
>> On 22 May 2014 20:22, Eduardo Valentin <edubezval@...il.com> wrote:
>> > However, on CPUs that needs thermal managment, it makes sense to have
>> > such dependency, from functional perspective. Mainly because scaling
>> > frequency and voltage up would be allowed only when thermal management
>> > is enabled.
>>
>> AFAIK, dependencies in KCONFIG are only for fixing compilation time issues.
>
> I do not think that's correct.
Yeah, that what I accepted later as well.. Dependency is whatever without which
the module is unusable.
And cpufreq-cpu0 is usable without THERMAL and so this dependency should
go away..
--
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