linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>, linux-omap@vger.kernel.org
Subject: Re: PM branch rebased to 2.6.29
Date: Fri, 20 Mar 2009 12:46:50 -0700	[thread overview]
Message-ID: <200903201246.51202.david-b@pacbell.net> (raw)
In-Reply-To: <20090320185927.GR29546@atomide.com>

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 ...


> > 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.

- Dave



  reply	other threads:[~2009-03-20 19:46 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18  5:21 PM branch rebased to 2.6.29 Kevin Hilman
2009-03-18  7:41 ` Artem Bityutskiy
2009-03-18 15:51   ` Kevin Hilman
2009-03-19 22:20 ` David Brownell
2009-03-20 18:59   ` Tony Lindgren
2009-03-20 19:46     ` David Brownell [this message]
2009-03-20 19:57       ` Tony Lindgren
2009-03-20 21:27         ` Tony Lindgren
2009-03-20 22:36       ` David Brownell
2009-03-24 17:10 ` Peter Barada
2009-03-24 18:08   ` Kevin Hilman
2009-03-24 20:11     ` Peter Barada
2009-03-24 20:21       ` Kevin Hilman
2009-03-24 20:37         ` Peter Barada
2009-03-27 20:50         ` Russ Dill
2009-03-30 10:08           ` Premi, Sanjeev
2009-03-30 10:42             ` Koen Kooi
2009-03-30 13:22               ` Premi, Sanjeev
2009-03-30 17:44             ` Russ Dill
2009-03-30 17:57               ` Kevin Hilman
2009-03-30 18:18                 ` Peter Barada
2009-03-30 18:43               ` Kevin Hilman
2009-03-30 23:01                 ` Russ Dill
2009-03-31  7:01                   ` Russ Dill
2009-03-31 18:25                   ` Kevin Hilman
2009-03-31 21:31                     ` Russ Dill
2009-03-31 23:33                       ` Kevin Hilman
2009-04-01  1:30                         ` Russ Dill
2009-04-01  4:11                           ` Kevin Hilman
2009-03-26 16:54 ` Jean Pihet
2009-03-26 17:01   ` Kevin Hilman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200903201246.51202.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).