From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 2/2] ARM: shmobile: ape6evm-reference: add CPUFreq support
Date: Wed, 10 Jul 2013 00:59:13 +0000 [thread overview]
Message-ID: <20130710005913.GF32603@verge.net.au> (raw)
In-Reply-To: <1373299498-10044-3-git-send-email-g.liakhovetski@gmx.de>
On Mon, Jul 08, 2013 at 06:04:58PM +0200, Guennadi Liakhovetski wrote:
> Add CPUFreq support to ape6evm-reference, using a max8973 regulator, that
> is supplying V_DVFS for the 4 CA15 cores on r8a73a4.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
> ---
>
> v3: call platform_device_register_simple() directly
>
> arch/arm/boot/dts/r8a73a4-ape6evm-reference.dts | 22 ++++++++++++++++++++++
> arch/arm/mach-shmobile/board-ape6evm-reference.c | 2 ++
> 2 files changed, 24 insertions(+), 0 deletions(-)
Thanks, I have queued this up for v3.12 in the dt-ape6evm branch
with Magnus's Ack. It should appear in renesas-next-20130710
prev parent reply other threads:[~2013-07-10 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 16:04 [PATCH v3 2/2] ARM: shmobile: ape6evm-reference: add CPUFreq support Guennadi Liakhovetski
2013-07-10 0:59 ` Simon Horman [this message]
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=20130710005913.GF32603@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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).