From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] ARM: rockchip: cpufreq-cpu0 device
Date: Mon, 29 Sep 2014 11:43:37 +0200 [thread overview]
Message-ID: <201717175.L17Ccvmpek@phil> (raw)
In-Reply-To: <7172632.O1FfdvXn6k@phil>
Hi Arnd, Olof,
this one patch adds a platform-device for cpufreq-cpu0 to mach-rockchip,
enabling frequency scaling using this cpufreq driver.
While it could be small enough to simply be included in the dt branch,
I didn't want to take that decision on my own :-)
So please pull
The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v3.18-rockchip-cpufreqdev
for you to fetch changes up to 47b06fc2d97a0d98d6053357561f2953d6547d25:
ARM: rockchip: add a cpufreq-cpu0 device (2014-09-29 09:21:38 +0200)
----------------------------------------------------------------
Add a simple cpufreq-cpu0 device for mach-rockchip
----------------------------------------------------------------
Heiko Stuebner (1):
ARM: rockchip: add a cpufreq-cpu0 device
arch/arm/mach-rockchip/rockchip.c | 7 +++++++
1 file changed, 7 insertions(+)
next prev parent reply other threads:[~2014-09-29 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 9:42 [GIT PULL 1/2] ARM: rockchip: cpu regulators and OPPs Heiko Stübner
2014-09-29 9:43 ` Heiko Stübner [this message]
2014-09-30 5:18 ` [GIT PULL 2/2] ARM: rockchip: cpufreq-cpu0 device Viresh Kumar
2014-09-30 10:15 ` [GIT PULL v2 " Heiko Stübner
2014-09-30 10:17 ` [PATCH] ARM: rockchip: honor renaming of cpufreq-cpu0 to cpufreq-dt Heiko Stübner
2014-11-04 6:02 ` [GIT PULL v2 2/2] ARM: rockchip: cpufreq-cpu0 device Olof Johansson
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=201717175.L17Ccvmpek@phil \
--to=heiko@sntech.de \
--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).