From: Geert Uytterhoeven <geert+renesas@glider.be> To: Simon Horman <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com> Cc: linux-renesas-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Geert Uytterhoeven <geert+renesas@glider.be> Subject: [PATCH 3/4] arm64: dts: r8a7795: Link ARM GIC to clock and clock domain Date: Tue, 17 Jan 2017 13:49:19 +0100 [thread overview] Message-ID: <1484657360-13101-4-git-send-email-geert+renesas@glider.be> (raw) In-Reply-To: <1484657360-13101-1-git-send-email-geert+renesas@glider.be> Link the ARM GIC to the INTC-AP module clock, and add it to the SYSC "always-on" PM Domain, so it can be power managed using that clock. Note that currently the GIC-400 driver doesn't support module clocks nor Runtime PM, so this must be handled as a critical clock. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- arch/arm64/boot/dts/renesas/r8a7795.dtsi | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi index 026a16ac41b422a1..0627df2a0b810c86 100644 --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi @@ -166,6 +166,9 @@ <0x0 0xf1060000 0 0x20000>; interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>; + clocks = <&cpg CPG_MOD 408>; + clock-names = "clk"; + power-domains = <&sysc R8A7795_PD_ALWAYS_ON>; }; wdt0: watchdog@e6020000 { -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: geert+renesas@glider.be (Geert Uytterhoeven) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 3/4] arm64: dts: r8a7795: Link ARM GIC to clock and clock domain Date: Tue, 17 Jan 2017 13:49:19 +0100 [thread overview] Message-ID: <1484657360-13101-4-git-send-email-geert+renesas@glider.be> (raw) In-Reply-To: <1484657360-13101-1-git-send-email-geert+renesas@glider.be> Link the ARM GIC to the INTC-AP module clock, and add it to the SYSC "always-on" PM Domain, so it can be power managed using that clock. Note that currently the GIC-400 driver doesn't support module clocks nor Runtime PM, so this must be handled as a critical clock. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- arch/arm64/boot/dts/renesas/r8a7795.dtsi | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi index 026a16ac41b422a1..0627df2a0b810c86 100644 --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi @@ -166,6 +166,9 @@ <0x0 0xf1060000 0 0x20000>; interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>; + clocks = <&cpg CPG_MOD 408>; + clock-names = "clk"; + power-domains = <&sysc R8A7795_PD_ALWAYS_ON>; }; wdt0: watchdog at e6020000 { -- 1.9.1
next prev parent reply other threads:[~2017-01-17 12:49 UTC|newest] Thread overview: 20+ 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 ` Geert Uytterhoeven 2017-01-17 12:49 ` [PATCH 1/4] ARM: dts: r8a7743: " Geert Uytterhoeven 2017-01-17 12:49 ` Geert Uytterhoeven 2017-01-17 12:49 ` [PATCH 2/4] ARM: dts: r8a7745: " Geert Uytterhoeven 2017-01-17 12:49 ` Geert Uytterhoeven 2017-01-17 12:49 ` Geert Uytterhoeven [this message] 2017-01-17 12:49 ` [PATCH 3/4] arm64: dts: r8a7795: " Geert Uytterhoeven 2017-01-17 14:00 ` Ramesh Shanmugasundaram 2017-01-17 14:00 ` Ramesh Shanmugasundaram 2017-01-17 14:08 ` Geert Uytterhoeven 2017-01-17 14:08 ` Geert Uytterhoeven 2017-01-17 12:49 ` [PATCH 4/4] arm64: dts: r8a7796: " Geert Uytterhoeven 2017-01-17 12:49 ` Geert Uytterhoeven 2017-01-23 9:23 ` [PATCH 0/4] ARM/arm64: dts: renesas: " Simon Horman 2017-01-23 9:23 ` Simon Horman 2017-01-23 9:26 ` Geert Uytterhoeven 2017-01-23 9:26 ` Geert Uytterhoeven 2017-01-23 9:42 ` Simon Horman 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=1484657360-13101-4-git-send-email-geert+renesas@glider.be \ --to=geert+renesas@glider.be \ --cc=horms@verge.net.au \ --cc=linux-arm-kernel@lists.infradead.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.