[PATCH/RFC 1/2] clk: renesas: Rework Kconfig and Makefile logic
Stephen Boyd
sboyd at codeaurora.org
Thu May 18 18:17:55 PDT 2017
On 04/25, Geert Uytterhoeven wrote:
> The goals are to:
> - Allow precise control over and automatic selection of which
> (sub)drivers are used for which SoC (which may change in the
> future),
> - Allow adding support for new SoCs easily,
> - Allow compile-testing of all (sub)drivers,
> - Keep driver selection logic in the subsystem-specific Kconfig
> independent from the architecture-specific Kconfig (i.e. no "select"
> from arch/arm64/Kconfig.platforms), to avoid dependencies.
>
> This is implemented by:
> - Introducing Kconfig symbols for all drivers and sub-drivers,
> - Introducing the Kconfig symbol CLK_RENESAS, which is enabled
> automatically when building for a Renesas ARM platform, and which
> enables all required drivers without interaction of the user, based
> on SoC-specific ARCH_* symbols,
> - Allowing the user to enable any Kconfig symbol manually if
> COMPILE_TEST is enabled,
> - Using the new Kconfig symbols instead of the ARCH_* symbols to
> control compilation in the Makefile,
> - Always entering drivers/clk/renesas/ during the build.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas at glider.be>
> ---
Acked-by: Stephen Boyd <sboyd at codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
More information about the linux-arm-kernel
mailing list