From: geert+renesas@glider.be (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 04/13] ARM: dts: r8a7743: Add missing clock for secondary CA15 CPU core
Date: Thu, 12 Oct 2017 11:35:07 +0200 [thread overview]
Message-ID: <1507800916-11509-5-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1507800916-11509-1-git-send-email-geert+renesas@glider.be>
Currently only the primary CPU in the CA15 cluster has a clocks
property, while the secondary CPU core is driven by the same clock.
Add the missing clocks property to fix this.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
arch/arm/boot/dts/r8a7743.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/r8a7743.dtsi b/arch/arm/boot/dts/r8a7743.dtsi
index d541fd9ffafb34ce..e09517bce30db2e8 100644
--- a/arch/arm/boot/dts/r8a7743.dtsi
+++ b/arch/arm/boot/dts/r8a7743.dtsi
@@ -63,6 +63,7 @@
compatible = "arm,cortex-a15";
reg = <1>;
clock-frequency = <1500000000>;
+ clocks = <&cpg CPG_CORE R8A7743_CLK_Z>;
power-domains = <&sysc R8A7743_PD_CA15_CPU1>;
next-level-cache = <&L2_CA15>;
};
--
2.7.4
next parent reply other threads:[~2017-10-12 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1507800916-11509-1-git-send-email-geert+renesas@glider.be>
2017-10-12 9:35 ` Geert Uytterhoeven [this message]
2017-10-13 6:23 ` [PATCH 04/13] ARM: dts: r8a7743: Add missing clock for secondary CA15 CPU core Chris Paterson
2017-10-12 9:35 ` [PATCH 12/13] ARM: dts: r8a7794: Add missing clock for secondary CA7 " Geert Uytterhoeven
[not found] ` <1507800916-11509-8-git-send-email-geert+renesas@glider.be>
2017-10-16 9:42 ` [PATCH 07/13] ARM: dts: r8a7790: Add missing clocks for secondary CA15 CPU cores Simon Horman
[not found] ` <1507800916-11509-9-git-send-email-geert+renesas@glider.be>
2017-10-16 9:42 ` [PATCH 08/13] ARM: dts: r8a7790: Add clocks for CA7 " Simon Horman
2017-10-16 9:53 ` [PATCH 00/13] ARM: dts: renesas: Add missing clocks for ARM " 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=1507800916-11509-5-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--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).