From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: 2.6.32-rc1: spitz boots but suspend/resume is broken
Date: Fri, 2 Oct 2009 09:32:05 +0200 [thread overview]
Message-ID: <20091002073205.GA23986@pengutronix.de> (raw)
In-Reply-To: <20091002041015.GB1409@ucw.cz>
Hi,
On Fri, Oct 02, 2009 at 06:10:15AM +0200, Pavel Machek wrote:
> On Wed 2009-09-30 16:09:25, Dmitry Eremin-Solenikov wrote:
> > On Wed, Sep 30, 2009 at 4:06 PM, Pavel Machek <pavel@ucw.cz> wrote:
> > > Hi!
> > >
> > > matrix keyboard driver needs to be enabled, otherwise it seems ok.
> > >
> > > Unfortunately, it does not respond to power button in any visible way
> > > :-(. Any ideas what might be wrong/how to debug it?
> >
> > Enable gpio-keyboard driver, verify (or port power button to it :))
> > and check that
> > enable_wakeup is enabled.
>
> It seems neccessary tables for gpio-keyboard just are not there :-(.
>
> In the meantime, this allows easy switch to known-good driver. (Can we
> get it upstream until problem is fixed properly?)
>
> Unfortunately, that still does not fix suspend/resume. (Does it work
> for you?)
Are you using the serial console on spitz? If yes, this might be
interesting for you:
http://bugzilla.kernel.org/show_bug.cgi?id=14297
I ended up with a console with 9600 baud after resume. My system resumed
correctly, but I did not see anything.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2009-10-02 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 12:06 2.6.32-rc1: spitz boots but suspend/resume is broken Pavel Machek
2009-09-30 12:09 ` Dmitry Eremin-Solenikov
2009-09-30 12:10 ` Eric Miao
2009-09-30 20:12 ` Pavel Machek
2009-10-02 4:10 ` Pavel Machek
2009-10-02 7:32 ` Sascha Hauer [this message]
2009-10-02 21:03 ` Pavel Machek
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=20091002073205.GA23986@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).