From: Pavel Machek <pavel@ucw.cz>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Greg Kroah-Hartman <gregkh@suse.de>,
kyungmin.park@samsung.com, myungjoo.ham@gmail.com,
Len Brown <len.brown@intel.com>
Subject: Re: [RFC PATCH v3 1/2] PM / Core: suspend_again callback for suspend_ops.
Date: Thu, 12 May 2011 06:19:28 +0000 [thread overview]
Message-ID: <20110512061928.GB2460@localhost.ucw.cz> (raw)
In-Reply-To: <1305091105-27173-1-git-send-email-myungjoo.ham@samsung.com>
Hi!
> A system or a device may need to control suspend/wakeup events. It may
> want to wakeup the system after a predefined amount of time or at a
> predefined event decided while entering suspend for polling or delayed
> work. Then, it may want to enter suspend again if its predefined wakeup
> condition is the only wakeup reason and there is no outstanding events;
> thus, it does not wakeup the userspace unnecessary or unnecessary
> devices and keeps suspended as long as possible (saving the power).
>
> Enabling a system to wakeup after a specified time can be easily
> achieved by using RTC. However, to enter suspend again immediately
> without invoking userland and unrelated devices, we need additional
> features in the suspend framework.
Looks ok to me.
> /**
> * suspend_enter - enter the desired system sleep state.
> * @state: state to enter
> + * @pm_wkup_pending: indicates that the power transition in progress
> + * should be aborted.
> *
Wowels are cheap, I'd add them here.
--
(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-05-12 6:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 5:18 MyungJoo Ham
2011-05-11 5:18 ` [RFC PATCH v3 2/2] PM / Core: partial resume/suspend API for suspend_again users MyungJoo Ham
2011-05-12 6:19 ` Pavel Machek [this message]
2011-05-17 4:59 ` [PATCH v4 1/2] PM / Core: suspend_again callback for suspend_ops MyungJoo Ham
2011-05-17 4:59 ` [PATCH v4 2/2] PM / Core: partial resume/suspend API for suspend_again users MyungJoo Ham
2011-05-17 20:52 ` Rafael J. Wysocki
2011-05-18 5:58 ` MyungJoo Ham
2011-05-18 20:18 ` Rafael J. Wysocki
2011-05-17 20:40 ` [PATCH v4 1/2] PM / Core: suspend_again callback for suspend_ops Rafael J. Wysocki
2011-05-18 9:07 ` MyungJoo Ham
2011-05-18 20:20 ` Rafael J. Wysocki
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=20110512061928.GB2460@localhost.ucw.cz \
--to=pavel@ucw.cz \
--cc=gregkh@suse.de \
--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 \
/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®