From: Stephen Boyd <sboyd@codeaurora.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] clk: renesas: cpg-mssr: Migrate to CLK_IS_CRITICAL
Date: Fri, 20 Jan 2017 15:00:07 -0800 [thread overview]
Message-ID: <20170120230007.GD8009@codeaurora.org> (raw)
In-Reply-To: <1484657190-12838-2-git-send-email-geert+renesas@glider.be>
On 01/17, Geert Uytterhoeven wrote:
> When the Renesas CPG/MSSR driver was introduced, it was anticipated that
> critical clocks would be handled through a new CLK_ENABLE_HAND_OFF flag
> soon. However, CLK_ENABLE_HAND_OFF never made it upstream.
>
> Instead, commit 32b9b10961860860 ("clk: Allow clocks to be marked as
> CRITICAL") introduced CLK_IS_CRITICAL, a flag with slightly differing
> semantics. Still, it can be used to prevent e.g. the GIC module clock
> from being turned off, until the GIC-400 driver has full support for
> Runtime PM.
>
> Hence migrate the Renesas CPG/MSSR driver from CLK_ENABLE_HAND_OFF to
> CLK_IS_CRITICAL.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-01-20 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 12:46 [PATCH 0/2] clk: renesas: Use CLK_IS_CRITICAL to handle critical clocks Geert Uytterhoeven
2017-01-17 12:46 ` [PATCH 1/2] clk: renesas: cpg-mssr: Migrate to CLK_IS_CRITICAL Geert Uytterhoeven
2017-01-20 23:00 ` Stephen Boyd [this message]
2017-01-17 12:46 ` [PATCH 2/2] clk: renesas: mstp: Make INTC-SYS a critical clock Geert Uytterhoeven
2017-01-20 23:12 ` Stephen Boyd
2017-01-23 9:50 ` Geert Uytterhoeven
2017-01-20 23:00 ` [PATCH 0/2] clk: renesas: Use CLK_IS_CRITICAL to handle critical clocks Stephen Boyd
2017-01-23 9:34 ` Geert Uytterhoeven
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=20170120230007.GD8009@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
/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.