From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] cpufreq-dt: support for cluster level clock
Date: Tue, 3 Mar 2015 21:03:35 +0800 [thread overview]
Message-ID: <1425387817-11382-1-git-send-email-leo.yan@linaro.org> (raw)
Add support for cluster level clock domain for cpufreq-dt driver.
With this support, then cpufreq driver which using cpufreq-dt as
backend can easily apply on multi-clusters system with cluster
level clock domain.
The first patch has been back ported to 3.18 and tested on hikey
board, the second patch is only compiled successfully.
Leo Yan (2):
cpufreq-dt: support cluster level clock
ARM: mvebu: update cpufreq-dt's platform data
arch/arm/mach-mvebu/pmsu.c | 2 +-
drivers/cpufreq/Kconfig | 5 +++--
drivers/cpufreq/cpufreq-dt.c | 14 +++++++++++++-
include/linux/cpufreq-dt.h | 16 ++++++++++++----
4 files changed, 29 insertions(+), 8 deletions(-)
--
1.9.1
next reply other threads:[~2015-03-03 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 13:03 Leo Yan [this message]
2015-03-03 13:03 ` [PATCH 1/2] cpufreq-dt: support cluster level clock Leo Yan
2015-03-03 13:10 ` Viresh Kumar
2015-03-03 14:03 ` Leo Yan
2015-03-03 15:19 ` Viresh Kumar
2015-03-04 2:35 ` Leo Yan
2015-03-03 13:03 ` [PATCH 2/2] ARM: mvebu: update cpufreq-dt's platform data Leo Yan
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=1425387817-11382-1-git-send-email-leo.yan@linaro.org \
--to=leo.yan@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).