From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-pm@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 6/6] arm64: dts: r8a7795: Add SYSC PM domains
Date: Fri, 11 Mar 2016 08:34:11 +0900 [thread overview]
Message-ID: <20160310233411.GC7423@verge.net.au> (raw)
In-Reply-To: <1457551135-22078-7-git-send-email-geert+renesas@glider.be>
On Wed, Mar 09, 2016 at 08:18:55PM +0100, Geert Uytterhoeven wrote:
> Add a device node for the System Controller.
> Hook up the Cortex-A57 CPU cores and the Cortex-A57 and Cortex A53 L2
> caches/SCUs to their respective PM domains.
> Hook up all devices that are part of the CPG/MSSR Clock Domain to the
> SYSC "always-on" PM Domain.
[snip]
> + sysc: system-controller@e6180000 {
> + compatible = "renesas,r8a7795-sysc";
> + reg = <0 0xe6180000 0 0x0400>;
In table 9.2 of v0.51e of the documentation I see some registers
beyond the 0x400 range above. Perhaps it could be enlarged accordingly?
> + #power-domain-cells = <1>;
> + };
[snip]
next prev parent reply other threads:[~2016-03-10 23:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 19:18 [PATCH v3 0/6] ARM/arm64: dts: rcar: Add SYSC PM domains Geert Uytterhoeven
[not found] ` <1457551135-22078-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2016-03-09 19:18 ` [PATCH v3 1/6] ARM: dts: r8a7779: " Geert Uytterhoeven
2016-03-09 19:18 ` [PATCH v3 2/6] ARM: dts: r8a7790: " Geert Uytterhoeven
2016-03-09 19:18 ` [PATCH v3 3/6] ARM: dts: r8a7791: " Geert Uytterhoeven
2016-03-09 19:18 ` [PATCH v3 4/6] ARM: dts: r8a7793: " Geert Uytterhoeven
2016-03-09 19:18 ` [PATCH v3 5/6] ARM: dts: r8a7794: " Geert Uytterhoeven
2016-03-09 19:18 ` [PATCH v3 6/6] arm64: dts: r8a7795: " Geert Uytterhoeven
2016-03-10 23:34 ` Simon Horman [this message]
2016-03-11 8:01 ` Geert Uytterhoeven
2016-03-14 0:12 ` 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=20160310233411.GC7423@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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).