From: Jerome Brunet <jbrunet@baylibre.com> To: Michael Turquette <mturquette@baylibre.com>, Stephen Boyd <sboyd@codeaurora.org>, Kevin Hilman <khilman@baylibre.com> Cc: Jerome Brunet <jbrunet@baylibre.com>, linux-clk@vger.kernel.org, linux-amlogic@lists.infradead.org Subject: [PATCH 10/10] clk: move CLK_SET_RATE_GATE protection from prepare to enable Date: Thu, 18 May 2017 18:38:04 +0200 [thread overview] Message-ID: <20170518163804.14123-11-jbrunet@baylibre.com> (raw) In-Reply-To: <20170518163804.14123-1-jbrunet@baylibre.com> CLK_SET_RATE_GATE name suggest that the rate can be set when the provider is gated (disabled). With the current implementation, the rate can only be set when the provider is unprepared, while it should be allowed to set a prepared and disable provider. Fix this by moving the rate protection mechanism in the enable/disable core functions Signed-off-by: Jerome Brunet <jbrunet@baylibre.com> --- drivers/clk/clk.c | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c index 1db3ad28dd85..3e2eb21ca8cd 100644 --- a/drivers/clk/clk.c +++ b/drivers/clk/clk.c @@ -491,9 +491,6 @@ static void clk_core_unprepare(struct clk_core *core) if (WARN_ON(core->prepare_count == 1 && core->flags & CLK_IS_CRITICAL)) return; - if (core->flags & CLK_SET_RATE_GATE) - clk_core_rate_unprotect(core); - if (--core->prepare_count > 0) return; @@ -564,14 +561,6 @@ static int clk_core_prepare(struct clk_core *core) core->prepare_count++; - /* - * CLK_SET_RATE_GATE is a special case of clock protection - * Instead of a consumer protection, the provider is protecting - * itself when prepared - */ - if (core->flags & CLK_SET_RATE_GATE) - clk_core_rate_protect(core); - return 0; } @@ -716,6 +705,9 @@ static void clk_core_disable(struct clk_core *core) if (WARN_ON(core->enable_count == 1 && core->flags & CLK_IS_CRITICAL)) return; + if (core->flags & CLK_SET_RATE_GATE) + clk_core_rate_unprotect(core); + if (--core->enable_count > 0) return; @@ -791,6 +783,15 @@ static int clk_core_enable(struct clk_core *core) } core->enable_count++; + + /* + * CLK_SET_RATE_GATE is a special case of clock protection + * Instead of a consumer protection, the provider is protecting + * itself when enabled + */ + if (core->flags & CLK_SET_RATE_GATE) + clk_core_rate_protect(core); + return 0; } -- 2.9.4
WARNING: multiple messages have this Message-ID (diff)
From: jbrunet@baylibre.com (Jerome Brunet) To: linus-amlogic@lists.infradead.org Subject: [PATCH 10/10] clk: move CLK_SET_RATE_GATE protection from prepare to enable Date: Thu, 18 May 2017 18:38:04 +0200 [thread overview] Message-ID: <20170518163804.14123-11-jbrunet@baylibre.com> (raw) In-Reply-To: <20170518163804.14123-1-jbrunet@baylibre.com> CLK_SET_RATE_GATE name suggest that the rate can be set when the provider is gated (disabled). With the current implementation, the rate can only be set when the provider is unprepared, while it should be allowed to set a prepared and disable provider. Fix this by moving the rate protection mechanism in the enable/disable core functions Signed-off-by: Jerome Brunet <jbrunet@baylibre.com> --- drivers/clk/clk.c | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c index 1db3ad28dd85..3e2eb21ca8cd 100644 --- a/drivers/clk/clk.c +++ b/drivers/clk/clk.c @@ -491,9 +491,6 @@ static void clk_core_unprepare(struct clk_core *core) if (WARN_ON(core->prepare_count == 1 && core->flags & CLK_IS_CRITICAL)) return; - if (core->flags & CLK_SET_RATE_GATE) - clk_core_rate_unprotect(core); - if (--core->prepare_count > 0) return; @@ -564,14 +561,6 @@ static int clk_core_prepare(struct clk_core *core) core->prepare_count++; - /* - * CLK_SET_RATE_GATE is a special case of clock protection - * Instead of a consumer protection, the provider is protecting - * itself when prepared - */ - if (core->flags & CLK_SET_RATE_GATE) - clk_core_rate_protect(core); - return 0; } @@ -716,6 +705,9 @@ static void clk_core_disable(struct clk_core *core) if (WARN_ON(core->enable_count == 1 && core->flags & CLK_IS_CRITICAL)) return; + if (core->flags & CLK_SET_RATE_GATE) + clk_core_rate_unprotect(core); + if (--core->enable_count > 0) return; @@ -791,6 +783,15 @@ static int clk_core_enable(struct clk_core *core) } core->enable_count++; + + /* + * CLK_SET_RATE_GATE is a special case of clock protection + * Instead of a consumer protection, the provider is protecting + * itself when enabled + */ + if (core->flags & CLK_SET_RATE_GATE) + clk_core_rate_protect(core); + return 0; } -- 2.9.4
next prev parent reply other threads:[~2017-05-18 16:38 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-05-18 16:37 [PATCH 00/10] clk: implement clock rate protection mechanism Jerome Brunet 2017-05-18 16:37 ` Jerome Brunet 2017-05-18 16:37 ` [PATCH 01/10] clk: take the prepare lock out of clk_core_set_paren Jerome Brunet 2017-05-18 16:37 ` Jerome Brunet 2017-05-18 16:37 ` [PATCH 02/10] clk: add clk_core_set_phase_nolock function Jerome Brunet 2017-05-18 16:37 ` Jerome Brunet 2017-05-18 16:37 ` [PATCH 03/10] clk: rework calls to round and determine rate callbacks Jerome Brunet 2017-05-18 16:37 ` Jerome Brunet 2017-05-18 16:37 ` [PATCH 04/10] clk: add support for clock protection Jerome Brunet 2017-05-18 16:37 ` Jerome Brunet 2017-05-18 16:37 ` [PATCH 05/10] clk: add clk_set_rate_protect Jerome Brunet 2017-05-18 16:37 ` Jerome Brunet 2017-05-18 16:38 ` [PATCH 07/10] clk: cosmetic changes to clk_summary debugfs entry Jerome Brunet 2017-05-18 16:38 ` Jerome Brunet 2017-05-18 16:38 ` [PATCH 08/10] clk: fix incorrect usage of ENOSYS Jerome Brunet 2017-05-18 16:38 ` Jerome Brunet 2017-05-18 16:38 ` [PATCH 09/10] clk: fix CLK_SET_RATE_GATE with clock rate protection Jerome Brunet 2017-05-18 16:38 ` Jerome Brunet 2017-05-18 16:38 ` Jerome Brunet [this message] 2017-05-18 16:38 ` [PATCH 10/10] clk: move CLK_SET_RATE_GATE protection from prepare to enable Jerome Brunet 2017-05-19 10:05 ` [PATCH 00/10] clk: implement clock rate protection mechanism Jerome Brunet 2017-05-19 10:05 ` Jerome Brunet
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=20170518163804.14123-11-jbrunet@baylibre.com \ --to=jbrunet@baylibre.com \ --cc=khilman@baylibre.com \ --cc=linux-amlogic@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=mturquette@baylibre.com \ --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: linkBe 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.