From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] ARM: shmobile: ape6evm: add CPUFreq support
Date: Mon, 24 Jun 2013 21:58:03 +0400 [thread overview]
Message-ID: <51C888AB.8010304@cogentembedded.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1306241257190.19735@axis700.grange>
Hello.
On 06/24/2013 03:05 PM, Guennadi Liakhovetski wrote:
> This patch adds OPPs to the CA15 DT node and a max8973 DT node to support
> clock and voltage scaling, using the cpufreq-cpu0 CPUFreq driver.
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
> ---
> v2: Subject to Mark acking v2 of my max8973 DT patch, this should be the
> updated version of my original ape6evm CPUFreq patch. This version puts
> all max8973 regulator bindings directly under the respective I2C device
> node instead of creating 2 additional levels.
> arch/arm/boot/dts/r8a73a4-ape6evm.dts | 22 ++++++++++++++++++++++
> 1 files changed, 22 insertions(+), 0 deletions(-)
> diff --git a/arch/arm/boot/dts/r8a73a4-ape6evm.dts b/arch/arm/boot/dts/r8a73a4-ape6evm.dts
> index 4fb0102..27c5e06 100644
> --- a/arch/arm/boot/dts/r8a73a4-ape6evm.dts
> +++ b/arch/arm/boot/dts/r8a73a4-ape6evm.dts
> @@ -52,3 +52,25 @@
> };
> };
> };
> +
> +&i2c5 {
> + vdd_dvfs: max8973 at 1b {
> + compatible = "maxium,max8973";
Er, perhaps "maxim"? Or is there some other corporation I don't know
about?
WBR, Sergei
prev parent reply other threads:[~2013-06-24 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 11:05 [PATCH v2 3/4] ARM: shmobile: ape6evm: add CPUFreq support Guennadi Liakhovetski
2013-06-24 17:58 ` Sergei Shtylyov [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=51C888AB.8010304@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--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).