LKML Archive on lore.kernel.org help / color / mirror / Atom feed
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 4/4] clk: dt: st: Introduce clock domain documentation Date: Mon, 26 Jan 2015 11:14:00 +0000 [thread overview] Message-ID: <1422270840-3039-5-git-send-email-lee.jones@linaro.org> (raw) In-Reply-To: <1422270840-3039-1-git-send-email-lee.jones@linaro.org> Signed-off-by: Lee Jones <lee.jones@linaro.org> --- .../devicetree/bindings/clock/st/st,clk-domain.txt | 34 ++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 Documentation/devicetree/bindings/clock/st/st,clk-domain.txt diff --git a/Documentation/devicetree/bindings/clock/st/st,clk-domain.txt b/Documentation/devicetree/bindings/clock/st/st,clk-domain.txt new file mode 100644 index 0000000..7309937 --- /dev/null +++ b/Documentation/devicetree/bindings/clock/st/st,clk-domain.txt @@ -0,0 +1,34 @@ +STMicroelectronics Clock Domain + +ST hardware have a bunch of clocks which must not be turned off. +If drivers a) fail to obtain a reference to any of these or b) give +up a previously obtained reference during suspend, the common clk +framework will attempt to turn them off and the hardware will +subsequently die. The only way to recover from this failure is to +restart. + +To avoid either of these two scenarios from catastrophically +disabling the running system we have implemented a clock domain +where clocks are consumed and references are taken, thus preventing +them from being shut down by the framework. + +We use the generic clock bindings found in: + Documentation/devicetree/bindings/clock/clock-bindings.txt + +Required properties: +- compatible : Must be "st,clk-domain" + +Example: + +clk-domain { + compatible = "st,clk-domain"; + clocks = <&clk_s_c0_flexgen CLK_EXT2F_A9>, + <&clk_s_c0_flexgen CLK_COMPO_DVP>, + <&clk_s_c0_flexgen CLK_MMC_1>, + <&clk_s_c0_flexgen CLK_ICN_SBC>, + <&clk_s_c0_flexgen CLK_ICN_LMI>, + <&clk_s_c0_flexgen CLK_ICN_CPU>, + <&clk_s_c0_flexgen CLK_TX_ICN_DMU>, + <&clk_s_a0_flexgen CLK_IC_LMI0>, + <&clk_m_a9>; +}; -- 1.9.1
next prev parent reply other threads:[~2015-01-26 11:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-26 11:13 [PATCH 0/4] clk: st: New clock domain Lee Jones 2015-01-26 11:13 ` [PATCH 1/4] ARM: sti: stih407-family: Supply defines for CLOCKGEN A0 Lee Jones 2015-01-26 11:13 ` [PATCH 2/4] ARM: sti: stih407-family: Provide Clock Domain information Lee Jones 2015-01-26 11:13 ` [PATCH 3/4] clk: st: Provide a clock domain Lee Jones 2015-01-26 11:14 ` Lee Jones [this message] 2015-01-28 1:19 ` [PATCH 4/4] clk: dt: st: Introduce clock domain documentation Mike Turquette 2015-01-28 7:58 ` 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=1422270840-3039-5-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: linkBe 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).