All of lore.kernel.org
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [STLinux Kernel] [PATCH 0/4] clk: Provide support for always-on clocks
Date: Thu, 2 Apr 2015 11:52:09 +0100	[thread overview]
Message-ID: <20150402105209.GA9447@x1> (raw)
In-Reply-To: <20150402081210.GB3567@griffinp-ThinkPad-X1-Carbon-2nd>

On Thu, 02 Apr 2015, Peter Griffin 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.

It's already on my TODO list:

TODO:
  - Clock Domain
    - Once the clk domain driver has been accepted, remove early returns in SPI driver
    - Remove clk_ignore_unused from the DT files
    - Add LMI1 clk to STiH418

> 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.

Take a look at the third item on my TODO. :)

Yes Maxime, if you can test the set once I've completed item 3, that
would be splendid.

> Apart from that, for the series: -
>  Acked-by: Peter Griffin <peter.griffin@linaro.org>

Thanks Peter.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Peter Griffin <peter.griffin@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, mturquette@linaro.org,
	sboyd@codeaurora.org, kernel@stlinux.com,
	devicetree@vger.kernel.org
Subject: Re: [STLinux Kernel] [PATCH 0/4] clk: Provide support for always-on clocks
Date: Thu, 2 Apr 2015 11:52:09 +0100	[thread overview]
Message-ID: <20150402105209.GA9447@x1> (raw)
In-Reply-To: <20150402081210.GB3567@griffinp-ThinkPad-X1-Carbon-2nd>

On Thu, 02 Apr 2015, Peter Griffin 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.

It's already on my TODO list:

TODO:
  - Clock Domain
    - Once the clk domain driver has been accepted, remove early returns in SPI driver
    - Remove clk_ignore_unused from the DT files
    - Add LMI1 clk to STiH418

> 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.

Take a look at the third item on my TODO. :)

Yes Maxime, if you can test the set once I've completed item 3, that
would be splendid.

> Apart from that, for the series: -
>  Acked-by: Peter Griffin <peter.griffin@linaro.org>

Thanks Peter.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2015-04-02 10:52 UTC|newest]

Thread overview: 63+ 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 ` Lee Jones
2015-02-27 21:14 ` 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   ` Lee Jones
2015-02-27 21:14 ` [PATCH 2/4] ARM: sti: stih410-clocks: Identify critical clocks as always-on Lee Jones
2015-02-27 21:14   ` Lee Jones
2015-04-02  8:00   ` [STLinux Kernel] " Peter Griffin
2015-04-02  8:00     ` Peter Griffin
2015-04-02  8:00     ` Peter Griffin
2015-02-27 21:14 ` [PATCH 3/4] clk: Provide always-on clock support Lee Jones
2015-02-27 21:14   ` Lee Jones
2015-02-27 21:51   ` Lee Jones
2015-02-27 21:51     ` Lee Jones
2015-02-28  7:52   ` [STLinux Kernel] " Maxime Coquelin
2015-02-28  7:52     ` Maxime Coquelin
2015-02-28  7:52     ` Maxime Coquelin
2015-03-02  8:16     ` Lee Jones
2015-03-02  8:16       ` Lee Jones
2015-03-02  8:16       ` Lee Jones
2015-04-01  1:13       ` Michael Turquette
2015-04-01  1:13         ` Michael Turquette
2015-02-28  9:21   ` Jassi Brar
2015-02-28  9:21     ` Jassi Brar
2015-02-28  9:21     ` Jassi Brar
2015-03-02  8:36     ` Lee Jones
2015-03-02  8:36       ` Lee Jones
2015-03-02  8:36       ` Lee Jones
2015-03-02 10:08       ` Jassi Brar
2015-03-02 10:08         ` Jassi Brar
2015-03-02 10:08         ` Jassi Brar
2015-03-02 10:18         ` Lee Jones
2015-03-02 10:18           ` Lee Jones
2015-03-02 10:25           ` [STLinux Kernel] " Maxime Coquelin
2015-03-02 10:25             ` Maxime Coquelin
2015-03-02 10:25             ` Maxime Coquelin
2015-03-02 10:32             ` Lee Jones
2015-03-02 10:32               ` Lee Jones
2015-03-02 10:28           ` Jassi Brar
2015-03-02 10:28             ` Jassi Brar
2015-03-02 10:28             ` Jassi Brar
2015-03-02 10:40             ` Lee Jones
2015-03-02 10:40               ` Lee Jones
2015-04-01  1:42             ` Michael Turquette
2015-04-01  1:42               ` Michael Turquette
2015-04-01  1:42               ` Michael Turquette
2015-04-02  4:39               ` Jassi Brar
2015-04-02  4:39                 ` Jassi Brar
2015-04-02  7:10                 ` Lee Jones
2015-04-02  7:10                   ` Lee Jones
2015-02-27 21:14 ` [PATCH 4/4] clk: dt: Introduce binding for " Lee Jones
2015-02-27 21:14   ` Lee Jones
2015-04-02  8:12 ` [STLinux Kernel] [PATCH 0/4] clk: Provide support for always-on clocks Peter Griffin
2015-04-02  8:12   ` Peter Griffin
2015-04-02  8:12   ` Peter Griffin
2015-04-02  9:45   ` Gabriel Fernandez
2015-04-02  9:45     ` Gabriel Fernandez
2015-04-02 10:53     ` Lee Jones
2015-04-02 10:53       ` Lee Jones
2015-04-02 10:58     ` Lee Jones
2015-04-02 10:58       ` Lee Jones
2015-04-02 10:52   ` Lee Jones [this message]
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=20150402105209.GA9447@x1 \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.