From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC 0/4] ARM: shmobile: Add CPUFreq support for r8a7790-lager platform
Date: Fri, 28 Feb 2014 13:53:46 +0000 [thread overview]
Message-ID: <1649276.HB5pdkE1O7@avalon> (raw)
In-Reply-To: <1393456190-7870-1-git-send-email-bcousson@baylibre.com>
Hi Benoit,
On Thursday 27 February 2014 00:09:46 Benoit Cousson wrote:
> Hi Magnus,
>
> This not-yet-ready-to-merge series is adding CPUFreq support to Lager board.
>
> Due to the missing data for the OPP voltage values, a safe 1.0v value is
> used for all OPPs.
>
> At least this series can be used by Laurent to test the z-clock CCF node
> and the KICK bit fix I've just sent.
>
> Bottom-line, no real DVFS so far, but just DFS :-)
>
> Please note that this series is safe even in the case of Cortex A7 boot
> since the cpufreq-cpu0 driver is using the physical CPU@0 device node.
> In the case of CA7 boot, the first cpu will be the CPU@100, and thus
> the driver will fail at probe time due to the lack of CPU@0.
I'd like to test that on r8a7791, can I use the same parameters (voltages,
frequencies and OPPs) ?
> Benoit Cousson (4):
> ARM: dts: r8a7790-lager: Add VDD MPU regulator for DVFS
> ARM: dts: r8a7790-lager: Add DVFS parameters into cpu0 node for
> r8a7790
> ARM: shmobile: lager-reference: Add cpufreq-cpu0 device for CPUFreq
> support
> ARM: shmobile: Make r8a77900 CPUFreq capable
>
> arch/arm/boot/dts/r8a7790-lager.dts | 25 +++++++++++++++++++++++
> arch/arm/boot/dts/r8a7790.dtsi | 11 +++++++++++
> arch/arm/mach-shmobile/Kconfig | 2 ++
> arch/arm/mach-shmobile/board-lager-reference.c | 3 +++
> 4 files changed, 41 insertions(+)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-02-28 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 23:09 [RFC 0/4] ARM: shmobile: Add CPUFreq support for r8a7790-lager platform Benoit Cousson
2014-02-28 13:53 ` Laurent Pinchart [this message]
2014-02-28 14:15 ` Benoit Cousson
2014-02-28 14:54 ` Geert Uytterhoeven
2014-02-28 16:34 ` Benoit Cousson
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=1649276.HB5pdkE1O7@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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