From: Pavel Machek <pavel@ucw.cz>
To: Stanislav Brabec <utx@penguin.cz>
Cc: rpurdie@rpsys.net, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
Dirk@Opfer-Online.de, arminlitzel@web.de,
Cyril Hrubis <metan@ucw.cz>,
thommycheck@gmail.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
dbaryshkov@gmail.com, omegamoon@gmail.com, eric.miao@marvell.com,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: zaurus c3000 aka spitz: fix resume
Date: Mon, 7 Sep 2009 13:39:45 +0200 [thread overview]
Message-ID: <20090907113945.GN23450@elf.ucw.cz> (raw)
In-Reply-To: <1252243938.4136.26.camel@utx.utx.cz>
Hi!
> > sharpsl_pm.c code tries to read battery state very early during
> > resume, but those battery meters are connected on SPI and that's only
> > resumed way later.
> >
> > Replace the check with simple checking of battery fatal signal, that
> > actually works at this stage.
>
> Tested on:
> - SL-C3200
> - snapshot e07cccf4046978df10f2e13fe2b99b2f9b3a65db
> - Reverted: 15bce40cb3133bcc07d548013df97e4653d363c1 (manual merge)
> - Applied your patch.
> - Config is here:
> http://www.penguin.cz/~utx/zaurus/feed/images/spitz/config-2.6.31-rc9-spitz
>
> Here is a big progress:
> - Zaurus goes from resume.
Ouch, it seems Eric Miao's emails are currently bouncing :-(.
Pavel
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
ymiao3@marvell.com
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-09-07 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 5:28 Pavel Machek
2009-09-06 13:32 ` Stanislav Brabec
2009-09-07 11:39 ` Pavel Machek [this message]
2009-09-07 16:08 ` Eric Miao
2009-09-07 22:32 ` Pavel Machek
2009-09-06 18:04 ` Dmitry Eremin-Solenikov
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=20090907113945.GN23450@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Dirk@Opfer-Online.de \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=eric.miao@marvell.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=utx@penguin.cz \
/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
all inboxes | Powered by JetHome®