From: Arnd Bergmann <arnd@arndb.de>
To: Li Yang <leoli@freescale.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
devicetree@vger.kernel.org,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Jia Hongtao <hongtao.jia@freescale.com>,
Eduardo Valentin <edubezval@gmail.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Scott Wood <scottwood@freescale.com>
Subject: Re: [PATCH V3] cpufreq: qoriq: Register cooling device based on device tree
Date: Sat, 27 Feb 2016 00:16:35 +0100 [thread overview]
Message-ID: <3593471.QAyZdAuTcW@wuerfel> (raw)
In-Reply-To: <CADRPPNTeBXJBybGwm4jkS64nSyWg+oaod3KJbE_SqfdSuUCA_Q@mail.gmail.com>
On Friday 26 February 2016 17:07:09 Li Yang wrote:
>
> I don't have a perfect solution either. But I think this is still
> better than making cpufreq not usable. The cpufreq driver will print
> out an error message if thermal is not reachable. Maybe this can
> relief the confusion a little bit?
With my patch, the configuration will just force the cpufreq
driver to be a loadable module as well if thermal is a module,
so the dependency can be resolved by loading the thermal module first.
I think that is really the best way around the problem, and it
matches what other platforms do for the same problem.
Arnd
next prev parent reply other threads:[~2016-02-26 23:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 9:21 [PATCH V3] cpufreq: qoriq: Register cooling device based on device tree Jia Hongtao
[not found] ` <1448529671-48216-1-git-send-email-hongtao.jia-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-12-14 23:58 ` Rafael J. Wysocki
[not found] ` <1697588.dLcbZBRWO4-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2015-12-18 22:32 ` Arnd Bergmann
2016-01-11 14:54 ` 答复: " Hongtao Jia
2016-01-11 17:34 ` Scott Wood
2016-01-11 21:13 ` Arnd Bergmann
2016-02-26 18:04 ` Li Yang
2016-02-26 20:20 ` Arnd Bergmann
2016-02-26 23:07 ` Li Yang
2016-02-26 23:16 ` Arnd Bergmann [this message]
2016-02-26 23:31 ` Li Yang
[not found] ` <CADRPPNSASmfxS=BWKvOxGKyCiqno9YvOuAfBaHwKL-Y=jQ2Dzw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-27 0:04 ` Li Yang
2016-02-27 0:08 ` Scott Wood
[not found] ` <1456531704.5360.53.camel-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>
2016-02-27 0:41 ` Li Yang
2016-02-29 10:05 ` Arnd Bergmann
2016-02-29 14:33 ` Rafael J. Wysocki
2016-02-29 14:39 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3593471.QAyZdAuTcW@wuerfel \
--to=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=hongtao.jia@freescale.com \
--cc=leoli@freescale.com \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rjw@rjwysocki.net \
--cc=scottwood@freescale.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox