From: narmstrong@baylibre.com (Neil Armstrong)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] clk: meson: meson8b: mark clk81 as critical
Date: Wed, 24 May 2017 11:45:30 +0200 [thread overview]
Message-ID: <18cf4eec-0bd0-aefe-9736-1aadd3e40942@baylibre.com> (raw)
In-Reply-To: <20170524093932.5262-2-jbrunet@baylibre.com>
On 05/24/2017 11:39 AM, Jerome Brunet wrote:
> From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
>
> Disabling clk81 results in an immediate freeze of the whole system. This
> can happen "accidentally" when the last child-clock of clk81 is disabled
> (in this case the common clock framework also disables clk81, even if it
> was only enabled indirectly before).
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
> drivers/clk/meson/meson8b.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/meson/meson8b.c b/drivers/clk/meson/meson8b.c
> index e9985503165c..9d1aaf6e9ac6 100644
> --- a/drivers/clk/meson/meson8b.c
> +++ b/drivers/clk/meson/meson8b.c
> @@ -399,7 +399,7 @@ struct clk_gate meson8b_clk81 = {
> .ops = &clk_gate_ops,
> .parent_names = (const char *[]){ "mpeg_clk_div" },
> .num_parents = 1,
> - .flags = (CLK_SET_RATE_PARENT | CLK_IGNORE_UNUSED),
> + .flags = (CLK_SET_RATE_PARENT | CLK_IS_CRITICAL),
> },
> };
>
>
Acked-by: Neil Armstrong <narmstrong@baylibre.com>
next prev parent reply other threads:[~2017-05-24 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 9:39 [PATCH v2 0/2] clk: meson: mark clk81 as critical Jerome Brunet
2017-05-24 9:39 ` [PATCH v2 1/2] clk: meson: meson8b: " Jerome Brunet
2017-05-24 9:45 ` Neil Armstrong [this message]
2017-05-24 9:39 ` [PATCH v2 2/2] clk: gxbb: remove CLK_IGNORE_UNUSED from clk81 Jerome Brunet
2017-05-24 9:45 ` Neil Armstrong
2017-05-25 18:24 ` [PATCH v2 0/2] clk: meson: mark clk81 as critical Michael Turquette
2017-05-29 7:54 ` Neil Armstrong
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=18cf4eec-0bd0-aefe-9736-1aadd3e40942@baylibre.com \
--to=narmstrong@baylibre.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox