Thread (19 messages) 19 messages, 3 authors, 2015-07-08

[PATCH v2 7/9] ARM: multi_v7_defconfig: Enable support for PWM Regulators

From: Lee Jones <hidden>
Date: 2015-06-25 15:03:11
Also in: linux-devicetree, linux-pm, lkml

On Thu, 25 Jun 2015, Javier Martinez Canillas wrote:
On Thu, Jun 25, 2015 at 10:42 AM, Lee Jones [off-list ref] wrote:
quoted
On Wed, 24 Jun 2015, Javier Martinez Canillas wrote:
[...]
quoted
quoted
quoted
diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
index f632af0..6666973 100644
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_defconfig
@@ -365,6 +365,7 @@ CONFIG_REGULATOR_MAX8907=y
 CONFIG_REGULATOR_MAX8973=y
 CONFIG_REGULATOR_MAX77686=y
 CONFIG_REGULATOR_PALMAS=y
+CONFIG_REGULATOR_PWM=y
The current policy is to build as much as possible as a module in
multi_v7_defconfig. Since this is a tristate Kconfig symbol, could you
please change it to =m ?
I would prefer that it stays built-in.
Ok, I've no strong opinion on this. I was just mentioning what arm-soc
maintainers prefer nowadays.

May I ask what's the rationale for leaving this option built-in?
My view is that multi_v7 is used for prototyping, testing and to
ensure all of the vendors are playing nice together.  Hopefully
vendors aren't actually releasing kernels built with this defconfig!
During testing/prototyping time; installing and messing around with
modules is an over-head I can do without.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help