From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 5/7] ARM: dts: r8a7791-koelsch: Add DVFS parameters into cpu0 node for r8a7791
Date: Thu, 29 May 2014 16:01:40 +0000 [thread overview]
Message-ID: <538759E4.7000304@cogentembedded.com> (raw)
In-Reply-To: <5386E681.4070107@bp.renesas.com>
On 05/29/2014 11:49 AM, Gaku Inami wrote:
> Add needed information inside CPU0 for the generic cpufreq-cpu0 driver.
> - voltage-tolerance = 1%
> It reflects the tolerance for the CPU voltage defined inside the OPP
> table. Due to the lack of proper OPP definition, use an arbitrary safe
> value.
> - clock-latency = 300 us
> Approximate worst-case latency to do a full DVFS transition for every
> OPPs. Due to the lack of HW information, use an arbitrary safe value.
> Note: The term transition-latency will be more accurate to define this
> value since the clock transition latency is not the only parameter that
> will define the overall DVFS transition.
> - operating-points = < kHz - uV >
> List of 6 operating points. All of them are using the same voltage
> since DVS is not supported in R-CAR Gen2.
> - clocks
> phandle to the CPU clock source. This clock source is used for all the
> 2 CortexA15 located inside the same cluster.
> Signed-off-by: Gaku Inami <gaku.inami.xw@bp.renesas.com>
> ---
> arch/arm/boot/dts/r8a7791.dtsi | 11 +++++++++++
> 1 file changed, 11 insertions(+)
You're not touching the Koelsch code in this patch, why mention the board
name in the subject?
WBR, Sergei
next prev parent reply other threads:[~2014-05-29 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 7:49 [PATCH 5/7] ARM: dts: r8a7791-koelsch: Add DVFS parameters into cpu0 node for r8a7791 Gaku Inami
2014-05-29 16:01 ` Sergei Shtylyov [this message]
2014-05-30 0:37 ` Gaku Inami
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=538759E4.7000304@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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