From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] clk: mvebu: armada-37xx-periph: add DVFS support for cpu clocks
Date: Thu, 21 Dec 2017 15:12:54 -0800 [thread overview]
Message-ID: <20171221231254.GB7997@codeaurora.org> (raw)
In-Reply-To: <20171130134029.20751-4-gregory.clement@free-electrons.com>
On 11/30, Gregory CLEMENT wrote:
> When DVFS is enabled the CPU clock setting is done using an other set of
> registers.
>
> These Power Management registers are exposed through a syscon as they
> will also be used by other drivers such as the cpufreq.
>
> This patch add the possibility to modify the CPU frequency using the
> associate load level matching the target frequency. Then all the
> frequency switch is handle by the hardware.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
> ---
Applied to clk-next + a small fix to regmap getting to make it
shorter.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-12-21 23:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 13:40 [PATCH 0/3] Add DVFS support on CPU clock for Armada 37xx Gregory CLEMENT
2017-11-30 13:40 ` [PATCH 1/3] clk: mvebu: armada-37xx-periph: cosmetic changes Gregory CLEMENT
2017-12-21 23:12 ` Stephen Boyd
2017-11-30 13:40 ` [PATCH 2/3] clk: mvebu: armada-37xx-periph: prepare cpu clk to be used with DVFS Gregory CLEMENT
2017-12-21 23:12 ` Stephen Boyd
2017-11-30 13:40 ` [PATCH 3/3] clk: mvebu: armada-37xx-periph: add DVFS support for cpu clocks Gregory CLEMENT
2017-12-21 23:12 ` Stephen Boyd [this message]
2017-12-21 10:53 ` [PATCH 0/3] Add DVFS support on CPU clock for Armada 37xx Gregory CLEMENT
2017-12-21 23:13 ` Stephen Boyd
2017-12-22 10:02 ` Gregory CLEMENT
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=20171221231254.GB7997@codeaurora.org \
--to=sboyd@codeaurora.org \
--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).