From: Lee Jones <lee.jones@linaro.org>
To: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: lee.jones@linaro.org, kernel@stlinux.com, mturquette@linaro.org,
sboyd@codeaurora.org, devicetree@vger.kernel.org
Subject: [PATCH v3 2/4] ARM: sti: stih407-family: Add platform interconnects to always-on clk domain
Date: Tue, 24 Feb 2015 17:33:40 +0000 [thread overview]
Message-ID: <1424799222-9301-3-git-send-email-lee.jones@linaro.org> (raw)
In-Reply-To: <1424799222-9301-1-git-send-email-lee.jones@linaro.org>
Certain clocks should not be turned of by clk_disable_unused. Until
now we have been using the kernel command-line of the same name to
prevent common clk from turning off all clocks without a reference,
as this would ensure hardware lockup. This patch lists each
platform interconnect which needs to stay on to prevent the
aforementioned issue from arising.
Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
arch/arm/boot/dts/stih407-family.dtsi | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/stih407-family.dtsi b/arch/arm/boot/dts/stih407-family.dtsi
index c06a546..35c74c6 100644
--- a/arch/arm/boot/dts/stih407-family.dtsi
+++ b/arch/arm/boot/dts/stih407-family.dtsi
@@ -34,6 +34,21 @@
reg = <0x08761000 0x1000>, <0x08760100 0x100>;
};
+ /*
+ * ICNs are not visible/controllable in Linux, but references to their
+ * clocks must be obtained and retained or the platform will become
+ * irrecoverably unresponsive.
+ */
+ icn {
+ compatible = "clk-always-on";
+ clocks = <&clk_s_c0_flexgen CLK_ICN_SBC>,
+ <&clk_s_c0_flexgen CLK_ICN_CPU>,
+ <&clk_s_c0_flexgen CLK_ICN_LMI>,
+ <&clk_s_c0_flexgen CLK_TX_ICN_DMU>,
+ <&clk_s_a0_flexgen CLK_IC_LMI0>,
+ <&clk_s_c0_flexgen CLK_EXT2F_A9>;
+ };
+
scu@08760000 {
compatible = "arm,cortex-a9-scu";
reg = <0x08760000 0x1000>;
--
1.9.1
next prev parent reply other threads:[~2015-02-24 17:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 17:33 [PATCH v3 0/4] clk: st: New always-on clock domain Lee Jones
[not found] ` <1424799222-9301-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-02-24 17:33 ` [PATCH v3 1/4] ARM: sti: stih407-family: Supply defines for CLOCKGEN A0 Lee Jones
2015-02-24 17:42 ` [PATCH v3 0/4] clk: st: New always-on clock domain Lee Jones
2015-03-04 12:00 ` Lee Jones
2015-03-06 19:08 ` Mike Turquette
2015-03-09 9:28 ` Lee Jones
2015-03-25 4:11 ` Geert Uytterhoeven
[not found] ` <CAMuHMdV8_uKQQgYkRPFOBgrqgw_y9A7T84ukfgWZpJmTL0eFCQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-26 13:51 ` Lee Jones
2015-03-26 16:55 ` Geert Uytterhoeven
2015-03-26 19:38 ` Lee Jones
2015-04-02 8:31 ` Geert Uytterhoeven
2015-04-02 10:48 ` Lee Jones
2015-02-24 17:33 ` Lee Jones [this message]
2015-02-24 17:33 ` [PATCH v3 3/4] clk: Provide an always-on clock domain framework Lee Jones
2015-02-24 17:33 ` [PATCH v3 4/4] clk: dt: Introduce always-on clock domain documentation Lee Jones
2015-02-27 21:37 ` [PATCH v3 0/4] clk: st: New always-on clock domain Robert Jarzmik
2015-02-27 21:49 ` Lee Jones
2015-02-27 23:38 ` Robert Jarzmik
2015-03-02 8:30 ` Lee Jones
2015-03-02 11:29 ` Robert Jarzmik
2015-03-02 11:37 ` Lee Jones
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=1424799222-9301-3-git-send-email-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.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).