From: Viresh Kumar <viresh.kumar@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org, Mason <slash.tmp@free.fr>,
linux-pm <linux-pm@vger.kernel.org>
Subject: Re: [PATCH RFC] Add cpufreq support
Date: Mon, 8 Feb 2016 18:01:12 +0530 [thread overview]
Message-ID: <20160208123111.GE8294@vireshk> (raw)
In-Reply-To: <2425296.hvcP5NDLXy@wuerfel>
On 08-02-16, 13:24, Arnd Bergmann wrote:
> Whatever you want to do in drivers/cpufreq that keeps this out of arch/arm/
>
> As I have said numerous times, there is absolutely no point in having a
> platform device for this, but if you insist on having one
No, I don't insist on that. I just hate it.
But the problem was that we never agreed to a way, by which we could
have probed cpufreq-dt. We were talking about compatible string from
'opp-v2' earlier, but that was soon discarded.
> just write one
> file that has an early_initcall() function and move all the code creating
> those devices in there for platforms using DT, e.g. by matching on the
> root compatible string the same way the platform code does today.
>
> For new platforms, please come up with a way to not need that and create
> a generic binding that anyone can follow.
Do you have any suggestions ?
- We aren't allowed to (re)use opp-v2 compatibility string
- We can't add a DT node for virtual device - cpufreq
What else can be done ?
--
viresh
next prev parent reply other threads:[~2016-02-08 12:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 16:58 [PATCH RFC] Add cpufreq support Mason
2016-02-05 22:24 ` Arnd Bergmann
2016-02-07 12:22 ` Viresh Kumar
2016-02-08 12:24 ` Arnd Bergmann
2016-02-08 12:31 ` Viresh Kumar [this message]
2016-02-08 12:34 ` Arnd Bergmann
2016-02-08 12:41 ` Viresh Kumar
2016-02-08 13:10 ` Arnd Bergmann
2016-02-08 13:16 ` Viresh Kumar
2016-02-08 13:45 ` Arnd Bergmann
2016-02-09 10:17 ` Mason
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=20160208123111.GE8294@vireshk \
--to=viresh.kumar@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=slash.tmp@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).