From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] clk: shmobile: Add R8A7740-specific clock support
Date: Fri, 23 May 2014 00:42:56 +0200 [thread overview]
Message-ID: <93388596.mpU9e50d0D@avalon> (raw)
In-Reply-To: <CAMuHMdUNpgn1ciHsvqWtEyn0RugxQTaCV+ki=S=5hUbmCjA6tg@mail.gmail.com>
Hi Geert,
On Wednesday 21 May 2014 17:50:35 Geert Uytterhoeven wrote:
> On Wed, May 21, 2014 at 5:41 PM, Laurent Pinchart wrote:
> >> +cpg_clocks: cpg_clocks at e6150000 {
> >> + compatible = "renesas,r8a7740-cpg-clocks";
> >> + reg = <0xe6150000 0x10000>;
> >
> > This range covers the MSTP registers. Unlike other Renesas SoCs with CCF
> > support in mainline, the MSTP registers are in the middle of the CPG
> > address space here, which is quite problematic.
>
> This is also the case for R-Car Gen2?!?
>
> /* Special CPG clocks */
> cpg_clocks: cpg_clocks at e6150000 {
> compatible = "renesas,r8a7791-cpg-clocks",
> "renesas,rcar-gen2-cpg-clocks";
> reg = <0 0xe6150000 0 0x1000>;
>
> mstp0_clks: mstp0_clks at e6150130 {
> compatible = "renesas,r8a7791-mstp-clocks",
> "renesas,cpg-mstp-clocks";
> reg = <0 0xe6150130 0 4>, <0 0xe6150030 0 4>;
Indeed :-/ It looks like we're just lucky that of_iomap() doesn't request the
memory resource.
Do you think it would make sense to move the MSTP nodes inside the CPG node to
better describe the hardware, and avoid future breakages if of_iomap() starts
calling request_resource() tomorrow ?
> Or perhaps I am misunderstanding what you mean?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-05-22 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 14:21 [PATCH v3] clk: shmobile: Add R8A7740-specific clock support Ulrich Hecht
2014-05-21 14:31 ` Geert Uytterhoeven
2014-05-21 15:41 ` Laurent Pinchart
2014-05-21 15:50 ` Geert Uytterhoeven
2014-05-22 22:42 ` Laurent Pinchart [this message]
2014-05-23 6:47 ` Geert Uytterhoeven
2014-05-22 0:37 ` Magnus Damm
2014-05-22 10:22 ` Laurent Pinchart
2014-05-22 11:16 ` Magnus Damm
2014-05-22 23:18 ` Laurent Pinchart
2014-05-26 4:30 ` Magnus Damm
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=93388596.mpU9e50d0D@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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