On Thu, Oct 08, 2009 at 22:42:01, Kevin Hilman wrote: [...]
> > I must admit to having a strong dislike of the HAS_XXX #ifdeffery, so > it should necessarly be used as the model to build on. > > If we didn't have mux conflicts, I'm sure we would all prefer to see > this all done with runtime detection. > > To me all of this boils down to how to deal with mutually exclusive > drivers. > > The existing approach was to let the Kconfig options under the main UI > board one decide. The current one lets the driver options themselves > decide. In the case of the user trying to figure out which things are > conflicting and which to disable, having the options as a Kconfig > 'choice' under the UI board seems much more straightforward to me. > > So, here's my proposal, which basically keeps the existing Kconfig > options but adds the runtime detection of UI board as done in $SUBJECT > patch. > > In Kconfig, have a main 'UI board' heading as we do now, but it should > not be selectable since this can be done at runtime. Under there all > the options should be listed and the mutually-exclusive ones handled > using 'choice'. > > This way, the default config can always enable the NOR, NAND, MMC, fb > drivers themselves and the mutual-exclusion is handled at the UI board > level. Okay. I decided to break my patch into multiple pieces so the multiple issues addressed by it can be commented on individually. I just submitted the first two, these should form the basis for rest of the work on this. Thanks, Sekhar _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
