On Tue, Jan 29, 2013 at 12:00 AM, Olof Johansson <[email protected]> wrote: > On Mon, Jan 28, 2013 at 02:52:31PM +0100, Linus Walleij wrote: >> From: Linus Walleij <[email protected]> >> >> The pin controller is an inherent part of the SoC, without >> it the system will not boot, thus it needs to be selected >> from Kconfig. >> >> Cc: [email protected] >> Signed-off-by: Linus Walleij <[email protected]> >> --- >> Requesting ACK from ARM SoC on this patch. > > Acked-by: Olof Johansson <[email protected]>
Thanks! > ... but I wonder if this is growing out of hand. Since they will always > be selected (and required) for UX500_SOC_DB8500, why not just make them > silent options that default to y with that as a depend? So either I do it like this by using select FOO in the Kconfig for the affected SoC, or I just turn it around and make it depend on the affected SoC and select it to "y" default. It's like eating eggs from the little or big end or something. This current approach has the upside of not proliferating the SoC Kconfig symbol outside of the ARM tree, but I have no strong preference... All this stuff used to live in the arch/arm/mach-foo folders in the past, like the clocks you just have to default-enable it somehow. Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
