[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdbj6UH+ZJfCYD1DKQ=3Qa=Aho9M5EWyQG8mRg=GCDEmXA@mail.gmail.com>
Date: Wed, 15 Mar 2017 14:37:44 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Rafael Wysocki <rjw@...ysocki.net>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Zhang Rui <rui.zhang@...el.com>,
Eduardo Valentin <edubezval@...il.com>,
linaro-kernel <linaro-kernel@...ts.linaro.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH] cpufreq: dbx500: Manage cooling device from cpufreq driver
On Tue, Mar 14, 2017 at 6:18 AM, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> The best place to register the CPU cooling device is from the cpufreq
> driver as we would know if all the resources are already available or
> not. That's what is done for the cpufreq-dt.c driver as well.
>
> The cpu-cooling driver for dbx500 platform was just (un)registering
> with the thermal framework and that can be handled easily by the cpufreq
> driver as well and in proper sequence as well.
>
> Get rid of the cooling driver and its its users and manage everything
> from the cpufreq driver instead.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> ---
> Only compile tested.
Works fine. Nice cleanup, thanks!
Tested-by: Linus Walleij <linus.walleij@...aro.org>
Yours,
Linus Walleij
Powered by blists - more mailing lists