Hi, On Thursday 08 October 2015 01:10 AM, Ulf Hansson wrote: > On 7 October 2015 at 17:52, Tony Lindgren <tony@xxxxxxxxxxx> wrote: >> * Ulf Hansson <ulf.hansson@xxxxxxxxxx> [151007 06:46]: >>> On 7 October 2015 at 15:26, Tony Lindgren <tony@xxxxxxxxxxx> wrote: >>>>>> Good idea, how about something like the following? AFAIK that's the >>>>>> only .config option needed as MFD_SYSCON is selected by Kconfig >>>>>> already. >>> >>> Similar to MFD_SYSCON, why don't we have REGULATOR_PBIAS to be >>> selected when omap_hsmmc is being used? >>> >>> It seems like that should also be a patch for the rc, right!? >> >> Well selecting CONFIG_REGULATOR is still optional and force selecting >> drivers usually leads into randconfig build issues sooner or later. >> And we'd like to make everything into loadable modules eventually. > > I am not sure I get your point. Perhaps I was too vague in what I suggested. > > Unless we express the dependencies via Kconfig files (or perhaps via > updated defconfigs), how do you expect build/boot automated tools to > handle this? Both omap2plus_defconfig and multi_v7_defconfig has CONFIG_PBIAS_REGULATOR enabled [1]. I think by using *depends on* in Kconfig, we'll end up in the same issue faced by Russell (since even with that CONFIG_PBIAS_REGULATOR won't be enabled) and using *select* can lead to randconfig errors. [1] -> https://lkml.org/lkml/2015/9/3/119 Thanks Kishon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
