* Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> [111020 12:23]: > On Thu, Oct 20, 2011 at 10:22:19AM -0700, Tony Lindgren wrote: > > > Hmm, actually, can't we just pass the board specific configuration in > > the board specific .dts file and then it gets merged in with the > > arch independent DT node? > > I don't understand what an "arch independent DT node" would be? Well that's the standard non-Linux specific parts. Basically what's in the $Subject patch minus what you commented on earlier: > +- regulator-change-voltage: boolean, Output voltage can be changed by software > +- regulator-change-current: boolean, Output current can be chnaged by software > +- regulator-change-mode: boolean, Operating mode can be changed by software > +- regulator-change-status: boolean, Enable/Disable control for regulator exists > +- regulator-change-drms: boolean, Dynamic regulator mode switching is enabled > +- regulator-mode-fast: boolean, allow/set fast mode for the regulator > +- regulator-mode-normal: boolean, allow/set normal mode for the regulator > +- regulator-mode-idle: boolean, allow/set idle mode for the regulator > +- regulator-mode-standby: boolean, allow/set standby mode for the regulator > +- regulator-input-uV: Input voltage for regulator when supplied by another regulator > +- regulator-always-on: boolean, regulator should never be disabled We still need to figure out how to get the above board specific data to the device driver probe in a way where we can avoid having platform glue code. Any thoughts on that? Tony -- 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
