From: Johannes Berg <johannes@sipsolutions.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
Stephen Rothwell <sfr@linuxcare.com>
Subject: Re: [PATCH] apm-emulation: notify about all suspend events, not just apm invoked ones
Date: Fri, 21 Mar 2008 15:18:31 +0100 [thread overview]
Message-ID: <1206109111.16475.172.camel@johannes.berg> (raw)
In-Reply-To: <20080321132924.GD5331@ucw.cz>
[-- Attachment #1.1: Type: text/plain, Size: 924 bytes --]
Hi Pavel,
> > This revamps the apm-emulation code to get suspend notifications
> > regardless of what way pm_suspend() was invoked, whether via the
> > apm ioctl or via /sys/power/state. Also do some code cleanup and
> > add comments while at it.
>
> Does this actually change user-kernel ABI?
Not ABI, but there is a change in behaviour (which is the whole point of
this patch). Previously, tools using /sys/power/state would live in one
sandbox and tools using APM in another, not knowing about each other but
both influencing the system suspend state. This makes them actually know
about each other by making the APM emulation indicate all system sleep
events, even those done via /sys/power/state and not the APM emulation
itself.
> > +enum apm_suspend_state {
> > + SUSPEND_NONE,
> These are not passed to userspace, are they?
No, they're just for the internal state machine.
johannes
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2008-03-21 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 22:37 [PATCH] apm-emulation: notify about all suspend events, not just apm invoked ones Johannes Berg
2008-03-17 20:39 ` Rafael J. Wysocki
2008-03-17 20:57 ` [PATCH v6] " Johannes Berg
2008-03-21 13:29 ` [PATCH] " Pavel Machek
2008-03-21 14:18 ` Johannes Berg [this message]
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=1206109111.16475.172.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=sfr@linuxcare.com \
/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