On Thursday 21 June 2012, Stephen Warren wrote: > > It should never be necessary to add board-specific properties in the > > nodes that describe the SoC specific bits. What I was referring to > > is just moving the data that currently resides in the regulator > > driver into DT. > > I guess I must be misunderstanding that comment - there are many many > examples of boards adding properties to nodes that describe the SoC. For > example, the GPIOs used by SDHCI controllers, board-specific max clock > rates for SDHCI or I2C controllers, pinmux configuration properties, to > name just a few. The difference is that configuration is board specific, but capabilities of the hardware are soc specific. The regulator-compatible property identifies just the capabilities and the location of one regulator: Look at struct ab8500_regulator_info, everything in there describes the soc: min/max voltages, register banks, startup delay. Those are all things that we could in theory have in the .dtsi file describing the soc. The board specific settings on the other hand are about what to put into those registers and what voltage to use. From all I can tell, those settings belong into the node that actually uses the regulator, not the node that defines it. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
