Skip to content

Fixes for omap PM for making omap3 DT only

Tony Lindgren linux-arm-kernel linux-devicetree linux-omap 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 11 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 11 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 00/11] Fixes for omap PM for making omap3 DT only
Quoted 3 lines · Sebastian Reichel

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

Quoted 4 lines

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