Re: PM branch rebased to 2.6.29

[Tony Lindgren <tony@atomide.com>]

* David Brownell <david-b@pacbell.net> [090319 15:27]:
> On Tuesday 17 March 2009, Kevin Hilman wrote:
> > - Beagle: MMC regulator: unbalanced disables.  This happens on boot
> >   and during suspend/resume. I don't think this is related to the PM
> >   branch, but is probably in linux-omap HEAD also, but didn't test.
> 
> It is.  Other boards may see that too.  Two fixes:
> 
>  * Least hassle ... I think all these should merge to the
>    linux-omap tree in any case (and thence linux-pm):
> 
>     http://marc.info/?l=linux-omap&m=123699264117846&w=2
>     http://marc.info/?l=linux-omap&m=123699340818395&w=2
>     http://marc.info/?l=linux-omap&m=123705919713239&w=2

Pushed these. That way we'll end up with a working
2.6.29-omap1 :)

Dave, got a version of the third patch above against the
mainline kernel? That could be added to the omap3-boards
queue for the upcoming merge window.
 
>  * Or there are a number of regulator-framework patches
>    floating around, all of which fix the bug there...
> 
> The root cause of this is that u-boot leaves VMMC1 active,
> and the regulator framework doesn't cope with that yet.
> The stackdump is basically caused by self-inconsistencies
> in that framework.
> 
> The first fix lets the twl4030-power driver (not yet on
> track for mainline merge) undo that, so the regulator
> framework will no longer be confused.  That presumes a
> bunch of board-specific patches fix that issue.  (As
> well as setting up other power resources, e.g. so that
> CLKREQ behaves, which is the real goal of that patch.)
> 
> The second fix -- in some flavor -- is IMO still needed,
> since the first fix is just avoiding regulator framework
> bugs.  

To me it sounds like the regulator framework should eventually
handle the regulators left on by the bootloader. Just let me
know if some other patches are needed to l-o tree meanwhile.

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html