From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC 1/2] clk: renesas: Rework Kconfig and Makefile logic
Date: Thu, 18 May 2017 18:17:55 -0700 [thread overview]
Message-ID: <20170519011755.GB20170@codeaurora.org> (raw)
In-Reply-To: <1493137626-21404-2-git-send-email-geert+renesas@glider.be>
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@glider.be>
> ---
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-05-19 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 16:27 [PATCH/RFC 0/2] clk / soc: renesas: Rework Kconfig and Makefile logic Geert Uytterhoeven
2017-04-25 16:27 ` [PATCH/RFC 1/2] clk: " Geert Uytterhoeven
2017-05-19 1:17 ` Stephen Boyd [this message]
2017-04-25 16:27 ` [PATCH/RFC 2/2] soc: " Geert Uytterhoeven
2017-04-26 7:36 ` [PATCH/RFC 0/2] clk / " Simon Horman
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=20170519011755.GB20170@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).