mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <gregkh@suse.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	linux-pm@lists.linux-foundation.org,
	Len Brown <len.brown@intel.com>,
	"Jean Delvare (PC drivers core)" <khali@linux-fr.org>,
	"Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
	kyungmin.park@samsung.com, myungjoo.ham@gmail.com,
	LKML <linux-kernel@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [RFC PATCH v2 1/3] PM / Core: suspend_again callback for device PM.
Date: Wed, 27 Apr 2011 00:14:20 +0200	[thread overview]
Message-ID: <20110426221420.GC29092@elf.ucw.cz> (raw)
In-Reply-To: <20110426205745.GB20381@suse.de>

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

  reply	other threads:[~2011-04-26 22:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  8:28 [RFC PATCH] PM / Core: suspend_again cb for syscore_ops MyungJoo Ham
2011-04-20 10:36 ` Pavel Machek
2011-04-20 20:28 ` Rafael J. Wysocki
2011-04-21  7:03   ` MyungJoo Ham
     [not found] ` <1303781471-2477-1-git-send-email-myungjoo.ham@samsung.com>
2011-04-26 11:47   ` [RFC PATCH v2 1/3] PM / Core: suspend_again callback for device PM Rafael J. Wysocki
2011-04-26 13:17     ` Greg KH
2011-04-26 20:38       ` Pavel Machek
2011-04-26 20:49         ` Rafael J. Wysocki
2011-04-26 21:11           ` Pavel Machek
2011-04-26 21:36             ` Rafael J. Wysocki
2011-04-26 22:06               ` Pavel Machek
2011-04-26 20:57         ` Greg KH
2011-04-26 22:14           ` Pavel Machek [this message]
2011-04-26 20:35     ` Pavel Machek
2011-04-26 20:47       ` Rafael J. Wysocki
2011-04-26 21:06         ` Pavel Machek
2011-04-26 21:46           ` Rafael J. Wysocki
2011-04-26 22:10             ` Pavel Machek
2011-04-26 22:32             ` Rafael J. Wysocki
2011-04-27  6:36               ` MyungJoo Ham
2011-04-27  9:46                 ` Stanislav Brabec
2011-04-27 10:47                   ` MyungJoo Ham

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=20110426221420.GC29092@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ben-linux@fluff.org \
    --cc=gregkh@suse.de \
    --cc=khali@linux-fr.org \
    --cc=kyungmin.park@samsung.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=myungjoo.ham@gmail.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /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

Powered by JetHome