From: David Brownell <david-b@pacbell.net>
To: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/3] Adapt twl4030 power code to new twl4030 code
Date: Fri, 7 Nov 2008 16:05:35 -0800 [thread overview]
Message-ID: <200811071605.35623.david-b@pacbell.net> (raw)
In-Reply-To: <20081008064913.GA4542@codecarver.research.nokia.com>
On Tuesday 07 October 2008, Peter 'p2' De Schrijver wrote:
>
> > I don't quite know the details of what these
> > PM scripts are doing ... could they be misbehaving on Beagle,
> > so that they explain why "reboot" on RC8 fails?
>
> It might. At least the warmreset script might cause problems on Beagle.
> I'm not familiar enough with beagle to know for sure.
Just for the record, now that I finally got around to making
that experiment: if I disable CONFIG_TWL4030_POWER, "reset"
works again on my Beagle (with current GIT).
Exactly why it fails on Beagle but not on Overo (with twl5030
not twl4030), I don't know.
- Dave
--
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
next prev parent reply other threads:[~2008-11-08 0:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 14:34 [PATCH 0/3] Move twl4030 scripts to platform data Peter 'p2' De Schrijver
2008-10-07 14:34 ` [PATCH 1/3] Add twl4030 scripts to 3430sdp " Peter 'p2' De Schrijver
2008-10-07 14:34 ` [PATCH 2/3] Adapt twl4030 power code to new twl4030 code Peter 'p2' De Schrijver
2008-10-07 14:34 ` [PATCH 3/3] Add twl4030 power platform device Peter 'p2' De Schrijver
2008-10-07 16:19 ` [PATCH 2/3] Adapt twl4030 power code to new twl4030 code David Brownell
2008-10-08 6:49 ` Peter 'p2' De Schrijver
2008-10-08 7:16 ` David Brownell
2008-10-08 7:22 ` David Brownell
2008-11-08 0:05 ` David Brownell [this message]
2008-10-07 16:05 ` [PATCH 0/3] Move twl4030 scripts to platform data David Brownell
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=200811071605.35623.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=peter.de-schrijver@nokia.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