From: Khiem Nguyen <khiem.nguyen.xt@rvc.renesas.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Simon Horman <horms+renesas@verge.net.au>,
Magnus Damm <damm+renesas@opensource.se>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Toru Oishi <toru.oishi.zj@rvc.renesas.com>,
"Khiem Trong. Nguyen" <khiem.nguyen.xt@rvc.renesas.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] cpufreq: rcar: Enable CPUFreq support
Date: Tue, 10 May 2016 11:55:41 +0700 [thread overview]
Message-ID: <573169CD.8050607@rvc.renesas.com> (raw)
In-Reply-To: <5731664D.1030909@rvc.renesas.com>
This series enables CPUFreq support in available R-Car Gen3 SoC.
It depends on 2 series below:
[PATCH 0/4] clk: renesas: cpg-mssr: Add support for R-Car M3-W
[RFC 0/4] Add Z clock support
All comments are appreciated.
Khiem Nguyen (2):
cpufreq: rcar: Add support for R8A7795 SoC
cpufreq: rcar: Add support for R8A7796 SoC
drivers/cpufreq/cpufreq-dt-platdev.c | 2 ++
1 file changed, 2 insertions(+)
--
1.9.1
next parent reply other threads:[~2016-05-10 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1462372543-31835-1-git-send-email-geert+renesas@glider.be>
[not found] ` <5731664D.1030909@rvc.renesas.com>
2016-05-10 4:55 ` Khiem Nguyen [this message]
2016-05-10 4:57 ` [PATCH 1/2] cpufreq: rcar: Add support for R8A7795 SoC Khiem Nguyen
2016-05-10 4:59 ` [PATCH 2/2] cpufreq: rcar: Add support for R8A7796 SoC Khiem Nguyen
2016-05-10 5:07 ` Viresh Kumar
2016-05-10 5:07 ` [PATCH 1/2] cpufreq: rcar: Add support for R8A7795 SoC Viresh Kumar
2016-05-10 8:17 ` Geert Uytterhoeven
2016-05-10 8:19 ` Viresh Kumar
[not found] ` <573166EB.70908@rvc.renesas.com>
[not found] ` <5731678E.3080003@rvc.renesas.com>
2016-05-17 13:03 ` [RFC 4/4] arm64: dts: r8a7795: Add Z clock scaling support Geert Uytterhoeven
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=573169CD.8050607@rvc.renesas.com \
--to=khiem.nguyen.xt@rvc.renesas.com \
--cc=damm+renesas@opensource.se \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=toru.oishi.zj@rvc.renesas.com \
--cc=viresh.kumar@linaro.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).