From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
"Kavyasree Kotagiri" <kavyasree.kotagiri@microchip.com>,
<linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: COMMON_CLK_LAN966X should depend on SOC_LAN966
Date: Tue, 8 Mar 2022 16:52:53 +0100 [thread overview]
Message-ID: <20220308155253.aoedxrdke2l3homa@soft-dev3-1.localhost> (raw)
In-Reply-To: <eb102eae05e5667b9bd342a0c387f7f262d24bda.1645716471.git.geert+renesas@glider.be>
The 02/24/2022 16:29, Geert Uytterhoeven wrote:
>
> The LAN966x Generic Clock Controller is only present on Microchip
> LAN966x SoCs. Hence add a dependency on SOC_LAN966, to prevent asking
> the user about this driver when configuring a kernel without LAN966x SoC
> support.
Reviewed-by: Horatiu Vultur <horatiu.vultur@microchip.com>
>
> Fixes: 54104ee023333e3b ("clk: lan966x: Add lan966x SoC clock driver")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/clk/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index c390e26dadf471f5..1c82a3e1129d4342 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -232,6 +232,7 @@ config COMMON_CLK_GEMINI
>
> config COMMON_CLK_LAN966X
> bool "Generic Clock Controller driver for LAN966X SoC"
> + depends on SOC_LAN966 || COMPILE_TEST
> help
> This driver provides support for Generic Clock Controller(GCK) on
> LAN966X SoC. GCK generates and supplies clock to various peripherals
> --
> 2.25.1
>
--
/Horatiu
next prev parent reply other threads:[~2022-03-08 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 15:29 [PATCH] clk: COMMON_CLK_LAN966X should depend on SOC_LAN966 Geert Uytterhoeven
2022-03-08 15:24 ` Nicolas Ferre
2022-03-08 15:52 ` Horatiu Vultur [this message]
2022-03-12 3:28 ` 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=20220308155253.aoedxrdke2l3homa@soft-dev3-1.localhost \
--to=horatiu.vultur@microchip.com \
--cc=geert+renesas@glider.be \
--cc=kavyasree.kotagiri@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.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