linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: John Fremlin <chief@bandits.org>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "Acpi-PM (E-mail)"
	<linux-power@phobos.fachschaften.tu-muenchen.de>,
	<sfr@canb.auug.org.au>, <linuxppc-dev@lists.linuxppc.org>,
	<linux-arm-kernel@lists.arm.linux.org.uk>
Subject: pmevent patch and PM
Date: 02 May 2001 18:59:32 +0100	[thread overview]
Message-ID: <m23danaayj.fsf@boreas.yi.org.> (raw)
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDDD9D@orsmsx35.jf.intel.com>


Hi PM maintainers! ARM and PPC ppl, who is your PM maintainer?

"Grover, Andrew" <andrew.grover@intel.com> writes:

> ACPI has by far the richest set of capabilities. It is a superset of
> APM.  Therefore a combined APM/ACPI interface is going to look a lot
> like an ACPI interface.
>
> IMHO an abstracted interface at this point is overengineering. Maybe
> later it will make sense, though.

A simple event interface is presented with the pmevent patch. It is
very extensible. The individual PM system driver suggests an action to
be taken and identifies the event exactly. Any number of userspace
readers can therefore apply fine grained policy to specific events and
simultaneously handle unknown events reasonably well.

The pmevent patch is available here

        http://john.snoop.dk/programs/linux/offbutton

There are some badly done example bindings for APM (that part of the
patch needs to be cleaned up).  Will your PM driver be able to map
events well onto it? I hope it should remove the need for an PM driver
specific event interfaces.

Please take a look and comment.

[...]

--

	http://ape.n3.net

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2001-05-02 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4148FEAAD879D311AC5700A0C969E89006CDDD9D@orsmsx35.jf.intel.com>
2001-05-02 17:59 ` John Fremlin [this message]
2001-05-02 18:57   ` pmevent patch and PM Erik Mouw
2001-05-02 19:16     ` Russell King - ARM Linux
2001-05-03 19:38       ` Dave Jones

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=m23danaayj.fsf@boreas.yi.org. \
    --to=chief@bandits.org \
    --cc=andrew.grover@intel.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-power@phobos.fachschaften.tu-muenchen.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).