Re: PM branch rebased to 2.6.29

[Tony Lindgren <tony@atomide.com>]

* David Brownell <david-b@pacbell.net> [090320 12:46]:
> On Friday 20 March 2009, Tony Lindgren wrote:
> > * David Brownell <david-b@pacbell.net> [090319 15:27]:
> > > 
> > >  * 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 :)
> 
> I approve that message.  ;)
> 
> 
> > 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.
> 
> That patch was a bit messy ... combined the VPLL2 bits,
> and the twl4030-power bits.  The former can go to mainline,
> but only after the regulator framework updates for VPLL2;
> I'll make such a patch.  The latter needs twl4030-power to
> get to mainline ...

OK & thanks. 
 
> > > 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.
> 
> I may just prepare an mmc-twl4030 patch with ugly workarounds,
> since I'm getting the strong feeling that it'll take forever
> to get the regulator framework fixed in that area.
> 
> Meanwhile, I suggest merging the updated version of the Overo
> patch, as sent by Steve.

That should be now applied, looks like the MMC is still not
working though.

Tony