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 v3 0/4] clk: st: New always-on clock domain
Date: Tue, 24 Feb 2015 17:33:38 +0000 [thread overview]
Message-ID: <1424799222-9301-1-git-send-email-lee.jones@linaro.org> (raw)
v2 => v3:
- Ensure DT actually reflects h/w
- i.e. Nodes should not contain a mishmash of different IP
blocks, but should identify related h/w. In the current
example we use interconnects
- Change naming from clkdomain to clk-always-on
- Place "do not abuse" warning in documentation
v1 => v2:
- Turned the ST specific driver into a generic one
Hardware can 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.
*** BLURB HERE ***
Lee Jones (4):
ARM: sti: stih407-family: Supply defines for CLOCKGEN A0
ARM: sti: stih407-family: Add platform interconnects to always-on clk
domain
clk: Provide an always-on clock domain framework
clk: dt: Introduce always-on clock domain documentation
.../devicetree/bindings/clock/clk-always-on.txt | 35 ++++++++++++
arch/arm/boot/dts/stih407-family.dtsi | 15 ++++++
drivers/clk/Makefile | 1 +
drivers/clk/clk-always-on.c | 62 ++++++++++++++++++++++
include/dt-bindings/clock/stih407-clks.h | 4 ++
5 files changed, 117 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/clk-always-on.txt
create mode 100644 drivers/clk/clk-always-on.c
--
1.9.1
next reply other threads:[~2015-02-24 17:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 17:33 Lee Jones [this message]
2015-02-24 17:33 ` [PATCH v3 1/4] ARM: sti: stih407-family: Supply defines for CLOCKGEN A0 Lee Jones
2015-02-24 17:33 ` [PATCH v3 2/4] ARM: sti: stih407-family: Add platform interconnects to always-on clk domain Lee Jones
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-24 17:42 ` [PATCH v3 0/4] clk: st: New always-on clock domain Lee Jones
2015-02-27 21:37 ` 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
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
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
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-1-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 \
--subject='Re: [PATCH v3 0/4] clk: st: New always-on clock domain' \
/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
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).