From: robert.jarzmik@free•fr (Robert Jarzmik)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 0/4] clk: st: New always-on clock domain
Date: Fri, 27 Feb 2015 22:37:10 +0100 [thread overview]
Message-ID: <87385r3uk9.fsf@free.fr> (raw)
In-Reply-To: <1424799222-9301-1-git-send-email-lee.jones@linaro.org> (Lee Jones's message of "Tue, 24 Feb 2015 17:33:38 +0000")
Lee Jones <lee.jones@linaro•org> writes:
> 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.
Hi Lee,
I wonder why there is a need for a new clock when CLK_IGNORE_UNUSED does
exist. What is the usecase that is covered by this patchset which is not used by
CLK_IGNORE_UNUSED clock flag ?
And if that reason exists, I'd like to find it in the commit message.
Cheers.
--
Robert
next prev parent reply other threads:[~2015-02-27 21:37 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
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 [this message]
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=87385r3uk9.fsf@free.fr \
--to=robert.jarzmik@free$(echo .)fr \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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