From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: Plain DFS (no voltage scaling)
Date: Thu, 4 Feb 2016 08:53:53 +0530 [thread overview]
Message-ID: <20160204032353.GQ3469@vireshk> (raw)
In-Reply-To: <56B24634.6060001@free.fr>
On 03-02-16, 19:25, Mason wrote:
> The sunxi guys pointed me in the right direction.
>
> http://lxr.free-electrons.com/source/arch/arm/mach-sunxi/sunxi.c#L20
>
> Why isn't there a compatible string like other drivers?
>
> Such as
> compatible = "cpufreq-dt"
> which would enable cpufreq on the platform?
Because DT can't have nodes for virtual devices :(
--
viresh
next prev parent reply other threads:[~2016-02-04 3:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 21:11 Plain DFS (no voltage scaling) Mason
2016-02-03 2:10 ` Viresh Kumar
2016-02-03 15:35 ` Mason
2016-02-03 16:14 ` Viresh Kumar
2016-02-03 18:25 ` Mason
2016-02-04 3:23 ` Viresh Kumar [this message]
2016-02-03 15:07 ` Mason
2016-02-03 16:13 ` Viresh Kumar
2016-02-03 18:19 ` Mason
2016-02-04 3:23 ` Viresh Kumar
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=20160204032353.GQ3469@vireshk \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).