[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1316730422-20027-6-git-send-email-mturquette@ti.com>
Date: Thu, 22 Sep 2011 15:27:00 -0700
From: Mike Turquette <mturquette@...com>
To: linux-kernel@...r.kernel.org
Cc: linux-arm-kernel@...ts.infradead.org, jeremy.kerr@...onical.com,
broonie@...nsource.wolfsonmicro.com, tglx@...utronix.de,
linus.walleij@...ricsson.com, amit.kucheria@...aro.org,
dsaxena@...aro.org, patches@...aro.org,
linaro-dev@...ts.linaro.org, paul@...an.com,
grant.likely@...retlab.ca, sboyd@...inc.com,
shawn.guo@...escale.com, skannan@...cinc.com,
magnus.damm@...il.com, arnd.bergmann@...aro.org,
linux@....linux.org.uk, eric.miao@...aro.org,
richard.zhao@...aro.org
Subject: [PATCH v2 5/7] clk: Add Kconfig option to build all generic clk drivers
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Currently drivers for the generic clk subsystem must be selected by
platforms using them in order to enable build. When doing development on
the API or generic build time testing it is useful to be able to build
unused drivers in order to improve coverage so supply a Kconfig option
which allows this.
Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
---
No change since v1
drivers/clk/Kconfig | 11 ++++++++++-
1 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
index a78967c..95b42a3 100644
--- a/drivers/clk/Kconfig
+++ b/drivers/clk/Kconfig
@@ -1,4 +1,3 @@
-
config CLKDEV_LOOKUP
bool
select HAVE_CLK
@@ -9,6 +8,16 @@ config HAVE_MACH_CLKDEV
config GENERIC_CLK
bool
+config GENERIC_CLK_BUILD_TEST
+ bool "Build all generic clock drivers"
+ depends on EXPERIMENTAL && GENERIC_CLK
+ select GENERIC_CLK_FIXED
+ select GENERIC_CLK_GATE
+ help
+ Enable all possible generic clock drivers. This is only
+ useful for improving build coverage, it is not useful for
+ production kernel builds.
+
config GENERIC_CLK_FIXED
bool
depends on GENERIC_CLK
--
1.7.4.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists