On Fri, Jun 21, 2013 at 9:32 AM, Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Friday 21 June 2013, Joel A Fernandes wrote: >> I haven't come across this problem but- are you saying there is a >> shortcoming in Kbuild/Kconfig that selects an option even if its >> dependency is not met? > > Well, the shortcoming is that it lets you specify impossible > contraints. You get a warning from Kconfig when building > such a configuration, but then it continues. > >> The problem with defconfig is also too many options I feel for a common case. >> CONFIG_DMADEVICES=y >> CONFIG_TI_EDMA=y >> >> Most if not all future OMAPs from will use EDMA. Why not we can be >> explicit about it and just built it in anyway. If ARCH_OMAP and >> DMADEVICES are selected, then we can just build EDMA in by default. > > It's just not how we do things. Kconfig is a mess because we are > not consistent in the way this is done. > >> I agree maybe the option can be dropped from Davinci but I suggest >> let's keep it for OMAP. Is that ok? > > No, I would still like you to not add it to either one. I'm spending > a lot of my time tracking down incorrect 'select' statements and I'd > rather spend it in a different way. I've had to a number of 'select' > statements from OMAP in the past, please don't add any new ones > unless there is a strict build dependency (which normally should not > exist). I think we are talking about different things, I agree the 'select DMADEVICES' can be dropped but lets please keep the default y option (not adding new select statements, just saying that if someone select DMADEVICES in menuconfig and if they're ARCH_OMAP=1 , then default to EDMA). This will simply allow people to have a default. Thanks. Thanks Joel -- 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
