public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: PM branch rebased to 2.6.29
Date: Thu, 19 Mar 2009 15:20:55 -0700	[thread overview]
Message-ID: <200903191520.55565.david-b@pacbell.net> (raw)
In-Reply-To: <87bprz9zju.fsf@deeprootsystems.com>

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

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

  parent reply	other threads:[~2009-03-19 22:20 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 [this message]
2009-03-20 18:59   ` Tony Lindgren
2009-03-20 19:46     ` David Brownell
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=200903191520.55565.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    /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