* Pali Rohár <pali.ro...@gmail.com> [160102 13:39]: > On Saturday 02 January 2016 18:14:31 Tony Lindgren wrote: > > > The n900 specific code was based on something before the TI generic > > values were available I think. And the last time I looked at it I > > came to the conclusion the n900 specific code is no better. > > Hm... if generic values are better, why old values are still there (in > board n900 code)?
We never had PM working in a generic way for the legacy booting but relied on board specific configuration instead for the ones that did work. Probably not worth changing the board-*.c file configuration unless you want to test that the new generic settings work. > > Or did I miss something? Are you seeing some issues with PM with dts > > based code? > > I'm just asking why we have different code for DST and board... OK. Yeah no reason beyond somebody taking the time to verify that the generic settings work on n900 in legacy booting mode :) > > We can certainly add it to twl4030-power if it provides something > > that the "ti,twl4030-power-idle-osc-off" does not. > > But do we need 'compatible = "ti,twl4030-power-n900"' specification in > omap3-n900.dts file at all? Well that generally done to allow adding support for the board specific configuration if needed with a fallback to the generic configuration. That's used quite a bit, for example boards typically set the compatible to the specific board but still end up booting with a generic one sucha as "ti,omap3". Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html