From: Gabriel Fernandez <gabriel.fernandez@linaro.org>
To: Peter Griffin <peter.griffin@linaro.org>
Cc: Lee Jones <lee.jones@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Mike Turquette <mturquette@linaro.org>,
"kernel@stlinux.com" <kernel@stlinux.com>,
sboyd@codeaurora.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [STLinux Kernel] [PATCH 0/4] clk: Provide support for always-on clocks
Date: Thu, 2 Apr 2015 11:45:14 +0200 [thread overview]
Message-ID: <CAG374jDc6HsJhL4HqTgvnMU3AG9pXNYXyxr6gjZQkTODR-BHyQ@mail.gmail.com> (raw)
In-Reply-To: <20150402081210.GB3567@griffinp-ThinkPad-X1-Carbon-2nd>
Hi Peter, Lee,
With these series as they are, we need 'clk_ignore_unused' on
sthi407-b2120.dts and stih418-b2199.dts.
We have to modificate stih407-clock.dtsi and stih418-clock.dtsi in same way.
BR
Gabriel
On 2 April 2015 at 10:12, Peter Griffin <peter.griffin@linaro.org> wrote:
> Hi Lee,
>
> On Fri, 27 Feb 2015, Lee Jones wrote:
>
>> Some hardware contains bunches of clocks which must never 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
>> disable them and a platform can fail irrecoverably as a
>> result. Usually the only way to recover from these failures
>> is to reboot.
>>
>> To avoid either of these two scenarios from catastrophically
>> disabling an otherwise perfectly healthy running system,
>> clocks can be identified as always-on using this property
>> from inside a clocksource's node. The CLK_IGNORE_UNUSED
>> flag will be applied to each clock instance named in this
>> property, thus preventing them from being shut down by the
>> framework.
>
> Great stuff.
>
> One minor comment is that assuming this works on stih407 and stih410
> to the extent that the platform can now boot without clk_ignore_unused
> kenel parameter then you should have an additional patch to remove
> clk_ignore_unused from the default bootargs in stih407-b2120.dts and
> stih410-b2120.dts files.
>
> Maxime - Is it possible for you to test this series on stih418-b2199 as
> a well? As it could most likely also be removed from stih418-b2199.dts file
> to, but neither Lee or myself have the hardware to test.
>
> Apart from that, for the series: -
> Acked-by: Peter Griffin <peter.griffin@linaro.org>
>
> regards,
>
> Peter.
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2015-04-02 9:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 21:14 [PATCH 0/4] clk: Provide support for always-on clocks Lee Jones
2015-02-27 21:14 ` [PATCH 1/4] ARM: sti: stih407-family: Supply defines for CLOCKGEN A0 Lee Jones
2015-02-27 21:14 ` [PATCH 2/4] ARM: sti: stih410-clocks: Identify critical clocks as always-on Lee Jones
2015-04-02 8:00 ` [STLinux Kernel] " Peter Griffin
2015-02-27 21:14 ` [PATCH 3/4] clk: Provide always-on clock support Lee Jones
2015-02-27 21:51 ` Lee Jones
2015-02-28 7:52 ` [STLinux Kernel] " Maxime Coquelin
2015-03-02 8:16 ` Lee Jones
2015-04-01 1:13 ` Michael Turquette
2015-02-28 9:21 ` Jassi Brar
2015-03-02 8:36 ` Lee Jones
2015-03-02 10:08 ` Jassi Brar
2015-03-02 10:18 ` Lee Jones
2015-03-02 10:25 ` [STLinux Kernel] " Maxime Coquelin
2015-03-02 10:32 ` Lee Jones
2015-03-02 10:28 ` Jassi Brar
2015-03-02 10:40 ` Lee Jones
2015-04-01 1:42 ` Michael Turquette
2015-04-02 4:39 ` Jassi Brar
2015-04-02 7:10 ` Lee Jones
2015-02-27 21:14 ` [PATCH 4/4] clk: dt: Introduce binding for " Lee Jones
2015-04-02 8:12 ` [STLinux Kernel] [PATCH 0/4] clk: Provide support for always-on clocks Peter Griffin
2015-04-02 9:45 ` Gabriel Fernandez [this message]
2015-04-02 10:53 ` Lee Jones
2015-04-02 10:58 ` Lee Jones
2015-04-02 10:52 ` 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=CAG374jDc6HsJhL4HqTgvnMU3AG9pXNYXyxr6gjZQkTODR-BHyQ@mail.gmail.com \
--to=gabriel.fernandez@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=peter.griffin@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).