linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrice CHOTARD <patrice.chotard@st.com>
To: Alain Volmat <avolmat@me.com>,
	"mturquette@baylibre.com" <mturquette@baylibre.com>,
	"sboyd@kernel.org" <sboyd@kernel.org>,
	"lee.jones@linaro.org" <lee.jones@linaro.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: clk-flexgen: fix clock-critical handling
Date: Mon, 23 Mar 2020 09:20:08 +0000	[thread overview]
Message-ID: <f053f9c4-557c-d32b-7bc6-c3ff2c6fa966@st.com> (raw)
In-Reply-To: <20200322140740.3970-1-avolmat@me.com>

Hi Alain

On 3/22/20 3:07 PM, Alain Volmat wrote:
> Fixes an issue leading to having all clocks following a critical
> clocks marked as well as criticals.
>
> Fixes: fa6415affe20 ("clk: st: clk-flexgen: Detect critical clocks")
>
> Signed-off-by: Alain Volmat <avolmat@me.com>
> ---
>  drivers/clk/st/clk-flexgen.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/clk/st/clk-flexgen.c b/drivers/clk/st/clk-flexgen.c
> index 4413b6e04a8e..55873d4b7603 100644
> --- a/drivers/clk/st/clk-flexgen.c
> +++ b/drivers/clk/st/clk-flexgen.c
> @@ -375,6 +375,7 @@ static void __init st_of_flexgen_setup(struct device_node *np)
>  			break;
>  		}
>  
> +		flex_flags &= ~CLK_IS_CRITICAL;
>  		of_clk_detect_critical(np, i, &flex_flags);
>  
>  		/*


Reviewed-by: Patrice Chotard <patrice.chotard@st.com>

Thanks

Patrice

  reply	other threads:[~2020-03-23  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22 14:07 [PATCH] clk: clk-flexgen: fix clock-critical handling Alain Volmat
2020-03-23  9:20 ` Patrice CHOTARD [this message]
2020-05-27  8:14 ` Stephen Boyd

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=f053f9c4-557c-d32b-7bc6-c3ff2c6fa966@st.com \
    --to=patrice.chotard@st.com \
    --cc=avolmat@me.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.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;
as well as URLs for NNTP newsgroup(s).