From: Dmitry Torokhov <dtor@insightbb.com>
To: Daniel Drake <dsd@gentoo.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI: add internal event mechanism
Date: Thu, 14 Jun 2007 23:28:11 -0400 [thread overview]
Message-ID: <200706142328.12131.dtor@insightbb.com> (raw)
In-Reply-To: <20070601030628.642207B409F@zog.reactivated.net>
Hi Daniel,
On Thursday 31 May 2007 23:06, Daniel Drake wrote:
> This patch creates a new event system for communication between in-kernel
> ACPI drivers ("ievent"). It is simple - it should only be used to infrequently
> pass simple messages to a small audience.
>
> This is used in an upcoming patch which makes the ACPI video driver listen for
> lid open events from the button driver. I hope it is generic enough to be
> useful to other ACPI drivers in the future.
>
The same can be achieved within input layer framework (just register an input
handler latching onto EV_SW/SW_LID devices). Unless there are more users for
ACPI-specific implementation input layer might be better option.
--
Dmitry
prev parent reply other threads:[~2007-06-15 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 3:06 [PATCH] ACPI: add internal event mechanism Daniel Drake
2007-06-15 3:28 ` Dmitry Torokhov [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=200706142328.12131.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=dsd@gentoo.org \
--cc=linux-acpi@vger.kernel.org \
/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).