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: Tue, 26 Apr 2011 22:38:53 +0200 [thread overview]
Message-ID: <20110426203853.GC27140@elf.ucw.cz> (raw)
In-Reply-To: <20110426131737.GA13597@suse.de>
Hi!
> > To conclude, I'm not sure about the approach. In particular, I'm not sure
> > if the benefit is worth the effort and the resulting complications (ie. the
> > possibility of having to deal with wakeup signals not requested by user
> > space) seem to be a bit too far reaching.
> >
> > Greg, what do you think?
>
> I agree with you in that I don't think that this type of feature is
> valid at the moment.
Our current "solution" is low level suspend code on Zaurus directly
looking at charger state and doing the "wakeup or not" decision by hand.
> I don't understand why our current situation doesn't work, what are we
> lacking that is needed for these systems that we have not seen
> before?
It works, but it is ugly; and it seems samsung now needs similar
hacks.
> 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.
Pavel
--
(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:[~2011-04-26 20:38 UTC|newest]
Thread overview: 53+ 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 10:36 ` Pavel Machek
2011-04-20 20:28 ` Rafael J. Wysocki
2011-04-20 20:28 ` Rafael J. Wysocki
2011-04-21 7:03 ` MyungJoo Ham
2011-04-21 7:03 ` MyungJoo Ham
2011-04-26 1:31 ` [RFC PATCH v2 1/3] PM / Core: suspend_again callback for device PM MyungJoo Ham
2011-04-26 11:47 ` Rafael J. Wysocki
2011-04-26 13:17 ` Greg KH
2011-04-26 13:17 ` Greg KH
2011-04-26 20:38 ` Pavel Machek
2011-04-26 20:38 ` Pavel Machek [this message]
2011-04-26 20:49 ` Rafael J. Wysocki
2011-04-26 21:11 ` Pavel Machek
2011-04-26 21:11 ` Pavel Machek
2011-04-26 21:36 ` Rafael J. Wysocki
2011-04-26 21:36 ` Rafael J. Wysocki
2011-04-26 22:06 ` Pavel Machek
2011-04-26 22:06 ` Pavel Machek
2011-04-26 20:49 ` Rafael J. Wysocki
2011-04-26 20:57 ` Greg KH
2011-04-26 22:14 ` Pavel Machek
2011-04-26 22:14 ` Pavel Machek
2011-04-26 20:57 ` Greg KH
2011-04-26 20:35 ` Pavel Machek
2011-04-26 20:35 ` Pavel Machek
2011-04-26 20:47 ` Rafael J. Wysocki
2011-04-26 20:47 ` Rafael J. Wysocki
2011-04-26 21:06 ` Pavel Machek
2011-04-26 21:06 ` Pavel Machek
2011-04-26 21:46 ` Rafael J. Wysocki
2011-04-26 21:46 ` Rafael J. Wysocki
2011-04-26 22:10 ` Pavel Machek
2011-04-26 22:10 ` Pavel Machek
2011-04-26 22:10 ` Pavel Machek
2011-04-26 22:32 ` Rafael J. Wysocki
2011-04-26 22:32 ` Rafael J. Wysocki
2011-04-26 22:32 ` Rafael J. Wysocki
2011-04-27 6:36 ` MyungJoo Ham
2011-04-27 6:36 ` MyungJoo Ham
2011-04-27 6:36 ` MyungJoo Ham
2011-04-27 9:46 ` Stanislav Brabec
2011-04-27 9:46 ` Stanislav Brabec
2011-04-27 10:47 ` MyungJoo Ham
2011-04-27 10:47 ` MyungJoo Ham
2011-04-27 10:47 ` MyungJoo Ham
2011-04-27 9:46 ` Stanislav Brabec
2011-04-26 21:46 ` Rafael J. Wysocki
2011-04-26 21:06 ` Pavel Machek
2011-04-26 11:47 ` Rafael J. Wysocki
2011-04-26 1:31 ` [RFC PATCH v2 2/3] PM / Core: suspend_again support for I2C MyungJoo Ham
2011-04-26 1:31 ` [RFC PATCH v2 3/3] PM / Core: suspend_again support for platform_device 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=20110426203853.GC27140@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.