mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>,
	Kevin Hilman <khilman@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: meson: select COMMON_CLK
Date: Tue, 17 Nov 2020 09:33:43 +0100	[thread overview]
Message-ID: <96386e0a-b3dd-1247-cf61-b2009915ab2d@baylibre.com> (raw)
In-Reply-To: <20201116165853.544263-1-jbrunet@baylibre.com>

On 16/11/2020 17:58, Jerome Brunet wrote:
> This fix the recent removal of clock drivers selection.
> While it is not necessary to select the clock drivers themselves, we need
> to select a proper implementation of the clock API, which for the meson, is
> CCF
> 
> Fixes: ba66a25536dd ("arm64: meson: ship only the necessary clock controllers")
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
>  
>  This fix is a side effect of this 0day report:
>  https://lore.kernel.org/r/202011151309.DVCsUlLh-lkp@intel.com
>  It shows that we need to select an implementation of clk.h
> 
>  arch/arm64/Kconfig.platforms | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 329e22c09cad..484e81f39db7 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -151,6 +151,7 @@ config ARCH_MEDIATEK
>  
>  config ARCH_MESON
>  	bool "Amlogic Platforms"
> +	select COMMON_CLK
>  	select PINCTRL
>  	select PINCTRL_MESON
>  	select MESON_IRQ_GPIO
> 

Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      reply	other threads:[~2020-11-17  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 16:58 Jerome Brunet
2020-11-17  8:33 ` Neil Armstrong [this message]

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=96386e0a-b3dd-1247-cf61-b2009915ab2d@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®