Re: [PATCH] interconnect: Disallow interconnect core to be built as a module
From: Bjorn Andersson
Date: Thu Sep 12 2019 - 12:33:44 EST
On Thu, Aug 29, 2019 at 1:07 AM Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
> Building individual drivers as modules is fine but allowing a core
> framework to be built as a module makes it really complex and should be
> Whatever uses the interconnect core APIs must also be built as a module
> if interconnect core is built as module, else we will see compilation
> If another core framework (like cpufreq, clk, etc), that can't be built
> as module, needs to use interconnect APIs then we will start seeing
> compilation failures with allmodconfig configurations as the symbols
> (like of_icc_get()) used in other frameworks will not be available in
> the built-in image.
> Disallow the interconnect core to be built as a module to avoid all
> these issues.
Reviewed-by: Bjorn Andersson <bjorn.andersson@xxxxxxxxxx>
> Signed-off-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
> drivers/interconnect/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/drivers/interconnect/Kconfig b/drivers/interconnect/Kconfig
> index bfa4ca3ab7a9..b6ea8f0a6122 100644
> --- a/drivers/interconnect/Kconfig
> +++ b/drivers/interconnect/Kconfig
> @@ -1,6 +1,6 @@
> # SPDX-License-Identifier: GPL-2.0-only
> menuconfig INTERCONNECT
> - tristate "On-Chip Interconnect management support"
> + bool "On-Chip Interconnect management support"
> Support for management of the on-chip interconnects.