From: Magnus Damm <magnus.damm@gmail.com>
To: linux-clk@vger.kernel.org
Cc: kuninori.morimoto.gx@renesas.com, gaku.inami.xw@bp.renesas.com,
mturquette@baylibre.com, linux-sh@vger.kernel.org,
sboyd@codeaurora.org, horms@verge.net.au, geert@linux-m68k.org,
laurent.pinchart@ideasonboard.com,
Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH v3 00/04] Renesas R-Car Gen3 CPG support V3
Date: Fri, 28 Aug 2015 09:15:50 +0000 [thread overview]
Message-ID: <20150828091550.21731.85227.sendpatchset@little-apple> (raw)
Renesas R-Car Gen3 CPG support V3
[PATCH v3 01/04] clk: shmobile: Get rid of CONFIG_ARCH_SHMOBILE_MULTI
[PATCH v3 02/04] clk: shmobile: Make MSTP clock-output-names optional
[PATCH v3 03/04] clk: shmobile: Add Renesas R-Car Gen3 CPG support
[PATCH v3 04/04] clk: shmobile: rcar-gen3: Add CPG/MSTP Clock Domain support
This series is the first attempt to take the CCF code from the single patch:
"[PATCH 1/9] clk: shmobile: add Renesas R-Car Gen3 CPG support"
to a full series of various CCF related updates related to R-Car Gen3.
In this series patch 1 and 2 get rid of CONFIG_ARCH_SHMOBILE_MULTI kconfig
bits and converts the MSTP CCF driver to not rely on clock-output-names. The
latter may need a bit more work.
Patch 3 and 4 introduce an updated R-Car Gen3 CPG driver where I have reworked
the code to not depend on clock-output-names instead of using strings simply
rely on RCAR_GEN3_CLK_xxx. Those must match the ABI defined in SoC specific
indicies such as the ones included in r8a7795-clock.h.
Patch 3 most likely needs to be reworked further to incorporate earlier
feedback from CCF maintainers.
Comments are very welcome!
Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
Written to be picked up independently from other R-Car Gen3 patches.
Documentation/devicetree/bindings/clock/renesas,rcar-gen3-cpg-clocks.txt | 31 +
drivers/clk/Makefile | 2
drivers/clk/shmobile/Makefile | 23
drivers/clk/shmobile/clk-mstp.c | 15
drivers/clk/shmobile/clk-rcar-gen3.c | 254 ++++++++++
5 files changed, 304 insertions(+), 21 deletions(-)
next reply other threads:[~2015-08-28 9:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 9:15 Magnus Damm [this message]
2015-08-28 9:16 ` [PATCH v3 01/04] clk: shmobile: Get rid of CONFIG_ARCH_SHMOBILE_MULTI Magnus Damm
2015-08-28 19:59 ` Laurent Pinchart
2015-08-29 8:33 ` Magnus Damm
2015-08-28 9:16 ` [PATCH v3 02/04] clk: shmobile: Make MSTP clock-output-names optional Magnus Damm
2015-08-28 19:37 ` Laurent Pinchart
2015-08-28 21:05 ` Geert Uytterhoeven
2015-08-28 9:16 ` [PATCH v3 03/04] clk: shmobile: Add Renesas R-Car Gen3 CPG support Magnus Damm
2015-08-28 17:20 ` Stephen Boyd
2015-08-29 8:46 ` Geert Uytterhoeven
2015-08-29 9:31 ` Magnus Damm
2015-08-28 9:16 ` [PATCH v3 04/04] clk: shmobile: rcar-gen3: Add CPG/MSTP Clock Domain support Magnus Damm
2015-08-28 9:19 ` Geert Uytterhoeven
2015-08-28 9:21 ` Magnus Damm
2015-08-28 17:21 ` [PATCH v3 00/04] Renesas R-Car Gen3 CPG support V3 Stephen Boyd
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=20150828091550.21731.85227.sendpatchset@little-apple \
--to=magnus.damm@gmail.com \
--cc=gaku.inami.xw@bp.renesas.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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).