mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jerome Brunet <jbrunet@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>, khilman@baylibre.com
Cc: linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH RFC 3/6] clk: meson: g12a: mark fclk_div3 as critical
Date: Wed, 27 Mar 2019 11:51:42 +0100	[thread overview]
Message-ID: <345dd7e287ed07f4a84847ff024fce237c1380a1.camel@baylibre.com> (raw)
In-Reply-To: <20190327103308.25058-4-narmstrong@baylibre.com>

On Wed, 2019-03-27 at 11:33 +0100, Neil Armstrong wrote:
> On Amlogic Meson G12b platform, the fclk_div3 seems to be necessary for
> the system to operate correctly.
> 
> Disabling it cause the entire system to freeze, including peripherals.
> 
> This patch patch marks this clock as critical, fixing boot on G12b platforms.
> 
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
>  drivers/clk/meson/g12a.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/drivers/clk/meson/g12a.c b/drivers/clk/meson/g12a.c
> index 03b4c78f558f..d62ebcd2162d 100644
> --- a/drivers/clk/meson/g12a.c
> +++ b/drivers/clk/meson/g12a.c
> @@ -1062,6 +1062,16 @@ static struct clk_fixed_factor g12a_fclk_div3_div = {
>  		.ops = &clk_fixed_factor_ops,
>  		.parent_names = (const char *[]){ "fixed_pll" },
>  		.num_parents = 1,
> +		/*
> +		 * This clock is used by the resident firmware and is required
> +		 * by the platform to operate correctly.
> +		 * Until the following condition are met, we need this clock to
> +		 * be marked as critical:
> +		 * a) Mark the clock used by a firmware resource, if possible
> +		 * b) CCF has a clock hand-off mechanism to make the sure the
> +		 *    clock stays on until the proper driver comes along
> +		 */
> +		.flags = CLK_IS_CRITICAL,

The gate should be critical then, not the fixed_divider clock.
the fdiv3 gate is a child of this clock, so fdiv3 should still be able to gate
with this


>  	},
>  };
> 
>  

Could you CC me of the whole series next time, I prefer getting the all
context.


  reply	other threads:[~2019-03-27 10:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27 10:33 [PATCH RFC 0/6] arm64: Add initial support for Odroid-N2 Neil Armstrong
2019-03-27 10:33 ` [PATCH RFC 1/6] dt-bindings: clk: meson: add g12b periph clock controller bindings Neil Armstrong
2019-03-31  6:42   ` Rob Herring
2019-03-27 10:33 ` [PATCH RFC 2/6] clk: meson: g12a: Add support for G12B CPUB clocks Neil Armstrong
2019-03-27 10:33 ` [PATCH RFC 3/6] clk: meson: g12a: mark fclk_div3 as critical Neil Armstrong
2019-03-27 10:51   ` Jerome Brunet [this message]
2019-04-04 14:51     ` Neil Armstrong
2019-03-27 10:33 ` [PATCH RFC 4/6] dt-bindings: arm: amlogic: add G12B bindings Neil Armstrong
2019-03-31  6:42   ` Rob Herring
2019-03-27 10:33 ` [PATCH RFC 5/6] dt-bindings: arm: amlogic: add Odroid-N2 binding Neil Armstrong
2019-03-31  6:42   ` Rob Herring
2019-03-27 10:33 ` [PATCH RFC 6/6] arm64: dts: meson: Add minimal support for Odroid-N2 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=345dd7e287ed07f4a84847ff024fce237c1380a1.camel@baylibre.com \
    --to=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narmstrong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome