[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110426221420.GC29092@elf.ucw.cz>
Date: Wed, 27 Apr 2011 00:14:20 +0200
From: Pavel Machek <pavel@....cz>
To: Greg KH <gregkh@...e.de>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
linux-pm@...ts.linux-foundation.org,
Len Brown <len.brown@...el.com>,
"Jean Delvare (PC drivers core)" <khali@...ux-fr.org>,
"Ben Dooks (embedded platforms)" <ben-linux@...ff.org>,
kyungmin.park@...sung.com, myungjoo.ham@...il.com,
LKML <linux-kernel@...r.kernel.org>,
Alan Stern <stern@...land.harvard.edu>
Subject: Re: [RFC PATCH v2 1/3] PM / Core: suspend_again callback for
device PM.
Hi!
> > > What is the root problem that this is trying to solve?
> >
> > It is trying to fix machines that need to run periodic kernel tasks
> > even when user asked them to sleep. Zaurus needs to periodicaly wake
> > up to be able to charge battery in s2ram state, for example.
>
> That sounds like a bug in userspace you are trying to work around. Why
> not solve it there first?
Can you be more specific?
The userspace is standard Debian; or maybe even init=/bin/bash. I want
to sleep the machine before I move, so I do echo mem >
/sys/power/state, as I do on PC.
Then I do plug the machine into AC when I move near outlet. In PC,
embedded controller wakes up and starts charging. In Zaurus, it is
kernel (SPI+charging drivers) that wake up, start charging, and go
back to sleep.
Then I (the user) press the power button and get "bash#" back. Where
is the userspace bug?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists