* Sebastian Reichel <sre@xxxxxxxx> [140411 13:51]: > > I'm on vacation from tomorrow until next week's weekend, but I will > have a look the week after next (if still needed). OK > I have not yet read much of TWL/OMAP PM documentation, but I wonder > if it makes sense to move the powerscripting stuff into the DTS file > somehow. On a first look the added N900 tables in > drivers/mfd/twl4030-power.c seem like a step back to me. Need to think about it a bit more, but I think we can have generic scripts based on the tables in "Recommended Sleep Sequences for the Zoom Platform" pdf at: http://omappedia.com/wiki/File:Recommended_Sleep_Sequences_Zoom.pdf Then we can have a function that patches in board specific stuff as needed as changes to the generic rconfig table. I'll take a look at that, let's see how that works. If that works, the board specific increments to the generic data should be pretty small and the data can easily live in the twl4030-power.c with no need to stuff it into the .dts files. BTW, the situation is also a bit different from the original N900 kernel as we now have runtime PM and drivers can easily manage their regulators. Regards, 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
