From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM/arm64: dts: renesas: Link ARM GIC to clock and clock domain
Date: Mon, 23 Jan 2017 10:23:31 +0100 [thread overview]
Message-ID: <20170123092330.GF31651@verge.net.au> (raw)
In-Reply-To: <1484657360-13101-1-git-send-email-geert+renesas@glider.be>
On Tue, Jan 17, 2017 at 01:49:16PM +0100, Geert Uytterhoeven wrote:
> Hi Simon, Magnus,
>
> This patch series improves the topology description in DT of the ARM GIC
> on Renesas SoCs using the CPG/MSSR bindings (R-Car Gen3 and RZ/G).
> It links the GIC to its module clock, and adds it to the SYSC "always
> on" PM Domain.
>
> Note that currently the GIC-400 driver doesn't support module clocks nor
> Runtime PM, so this must be handled as a critical clock.
> As the CPG/MSSR driver, unlike the legacy MSTP driver, is already aware
> of critical clocks, this series can be applied right now.
Hi Geert,
does the note above imply that "[PATCH 0/2] clk: renesas: Use
CLK_IS_CRITICAL to handle critical clocks" is a dependency of this series?
next prev parent reply other threads:[~2017-01-23 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 12:49 [PATCH 0/4] ARM/arm64: dts: renesas: Link ARM GIC to clock and clock domain Geert Uytterhoeven
2017-01-17 12:49 ` [PATCH 1/4] ARM: dts: r8a7743: " Geert Uytterhoeven
2017-01-17 12:49 ` [PATCH 2/4] ARM: dts: r8a7745: " Geert Uytterhoeven
2017-01-17 12:49 ` [PATCH 3/4] arm64: dts: r8a7795: " Geert Uytterhoeven
2017-01-17 14:00 ` Ramesh Shanmugasundaram
2017-01-17 14:08 ` Geert Uytterhoeven
2017-01-17 12:49 ` [PATCH 4/4] arm64: dts: r8a7796: " Geert Uytterhoeven
2017-01-23 9:23 ` Simon Horman [this message]
2017-01-23 9:26 ` [PATCH 0/4] ARM/arm64: dts: renesas: " Geert Uytterhoeven
2017-01-23 9:42 ` 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=20170123092330.GF31651@verge.net.au \
--to=horms@verge.net.au \
--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;
as well as URLs for NNTP newsgroup(s).