From: Khiem Nguyen <khiem.nguyen.xt@rvc.renesas.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
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>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Toru Oishi <toru.oishi.zj@rvc.renesas.com>,
"Khiem Trong. Nguyen" <khiem.nguyen.xt@rvc.renesas.com>
Subject: [RFC 0/4] Add Z clock support
Date: Tue, 10 May 2016 11:40:45 +0700 [thread overview]
Message-ID: <5731664D.1030909@rvc.renesas.com> (raw)
In-Reply-To: <1462372543-31835-1-git-send-email-geert+renesas@glider.be>
Hi Geert,
This series adds Z clock support for R-Car Gen3.
It was written on top of "[PATCH 0/4] clk: renesas: cpg-mssr: Add
support for R-Car M3-W" series.
Dien Pham (1):
arm64: dts: r8a7795: Add Z clock scaling support
Khiem Nguyen (3):
clk: renesas: rcar-gen3-cpg: Add Z clock
clk: renesas: r8a7795: Add Z clock
clk: renesas: r8a7796: Add Z clock
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 26 ++++++
drivers/clk/renesas/r8a7795-cpg-mssr.c | 1 +
drivers/clk/renesas/r8a7796-cpg-mssr.c | 2 +
drivers/clk/renesas/rcar-gen3-cpg.c | 143
+++++++++++++++++++++++++++++++
drivers/clk/renesas/rcar-gen3-cpg.h | 1 +
5 files changed, 173 insertions(+)
--
1.9.1
next prev parent reply other threads:[~2016-05-10 4:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 14:35 [PATCH 0/4] clk: renesas: cpg-mssr: Add support for R-Car M3-W Geert Uytterhoeven
2016-05-04 14:35 ` [PATCH 2/4] clk: renesas: Add r8a7796 CPG Core Clock Definitions Geert Uytterhoeven
[not found] ` <1462372543-31835-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2016-05-04 14:35 ` [PATCH 1/4] clk: renesas: cpg-mssr: Document r8a7796 support Geert Uytterhoeven
2016-05-05 22:13 ` Rob Herring
2016-05-04 14:35 ` [PATCH 3/4] clk: renesas: cpg-mssr: Extract common R-Car Gen3 support code Geert Uytterhoeven
2016-05-04 14:35 ` [PATCH 4/4] clk: renesas: cpg-mssr: Add support for R-Car M3-W Geert Uytterhoeven
2016-05-10 4:40 ` Khiem Nguyen [this message]
2016-05-13 8:55 ` [RFC 0/4] Add Z clock support Geert Uytterhoeven
2016-05-10 4:42 ` [RFC 1/4] clk: renesas: rcar-gen3-cpg: Add Z clock Khiem Nguyen
2016-05-13 8:54 ` Geert Uytterhoeven
2016-09-23 8:32 ` Geert Uytterhoeven
2016-05-10 4:43 ` [RFC 2/4] clk: renesas: r8a7795: " Khiem Nguyen
2016-05-10 4:44 ` [RFC 3/4] clk: renesas: r8a7796: " Khiem Nguyen
2016-05-10 7:39 ` Geert Uytterhoeven
2016-05-10 4:46 ` [RFC 4/4] arm64: dts: r8a7795: Add Z clock scaling support Khiem Nguyen
2016-05-17 13:03 ` Geert Uytterhoeven
2016-05-13 8:55 ` [RFC 2/4] clk: renesas: r8a7795: Add Z clock Geert Uytterhoeven
2016-05-26 2:35 ` [PATCH 0/4] clk: renesas: cpg-mssr: Add support for R-Car M3-W Simon Horman
2016-05-26 6:55 ` Geert Uytterhoeven
2016-05-27 0:49 ` Simon Horman
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=5731664D.1030909@rvc.renesas.com \
--to=khiem.nguyen.xt@rvc.renesas.com \
--cc=damm+renesas@opensource.se \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=toru.oishi.zj@rvc.renesas.com \
/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).