All of lore.kernel.org
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] clk: Provide option to unprepare unused clocks at late init
Date: Thu, 20 Dec 2012 20:17:20 +0100	[thread overview]
Message-ID: <CACRpkdbCuDxszPZ-VYxhbNUSvyGM=rGw4h5Uy8LfqDcY0V-Dyg@mail.gmail.com> (raw)
In-Reply-To: <1355872583-20928-1-git-send-email-ulf.hansson@stericsson.com>

On Wed, Dec 19, 2012 at 12:16 AM, Ulf Hansson
<ulf.hansson@stericsson.com> wrote:

> The disable_unused sequence executed at late init, is already handling the
> fast unused ungated clocks to be gated. This patchset extends this sequence to
> include the slow unused prepared clocks to be unprepared.
>
> The default behavior will not change in this patchset. To unprepare unused
> clocks during the disable_unused sequence, the clk_hw needs to implement
> the new optional callback, is_prepared.
>
> The motivation for this patchset is to save power. Clocks that is from
> bootloaders prepared|enabled, but not used should be unprepared|disabled.

This has a nice symmetrical touch to it and looks allright to me, so
Acked-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij

  parent reply	other threads:[~2012-12-20 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 23:16 [PATCH 0/3] clk: Provide option to unprepare unused clocks at late init Ulf Hansson
2012-12-18 23:16 ` [PATCH 1/3] clk: Introduce optional is_prepared callback Ulf Hansson
2012-12-18 23:16 ` [PATCH 2/3] clk: Unprepare the unused prepared slow clocks at late init Ulf Hansson
2012-12-18 23:16 ` [PATCH 3/3] clk: Introduce optional unprepare_unused callback Ulf Hansson
2012-12-20 19:17 ` Linus Walleij [this message]
2013-01-16  8:54   ` [PATCH 0/3] clk: Provide option to unprepare unused clocks at late init Ulf Hansson

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='CACRpkdbCuDxszPZ-VYxhbNUSvyGM=rGw4h5Uy8LfqDcY0V-Dyg@mail.gmail.com' \
    --to=linus.walleij@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.