From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Pavel Machek <pavel@suse.cz>, Oliver Neukum <oliver@neukum.org>,
Richard Purdie <rpurdie@rpsys.net>,
James Simmons <jsimmons@pentafluge.infradead.org>,
Adrian Bunk <bunk@stusta.de>,
Linux Input Devices <linux-input@atrey.karlin.mff.cuni.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6: drivers/input/power.c is never built
Date: Fri, 18 Feb 2005 13:19:08 -0500 [thread overview]
Message-ID: <d120d50005021810195f16ac0d@mail.gmail.com> (raw)
In-Reply-To: <20050218170036.GA1672@ucw.cz>
On Fri, 18 Feb 2005 18:00:36 +0100, Vojtech Pavlik <vojtech@suse.cz> wrote:
> On Fri, Feb 18, 2005 at 05:01:53PM +0100, Pavel Machek wrote:
>
> > > > It has quite a lot of #ifdefs for CONFIG_APM/CONFIG_ARM/CONFIG_ACPI,
> > > > and it will not work on i386/APM, anyway. I still believe right
> > > > solution is to add input interface to ACPI. /proc/acpi/events needs to
> > > > die, being replaced by input subsystem.
> > >
> > > But aren't there power events (battery low, etc) which are not
> > > input events?
> >
> > Yes, there are. They can probably stay... Or we can get "battery low"
> > key.
>
> We even have an event class for that, EV_PWR in the input subsystem.
I really really think this is wrong. Power management should be
possible without input layer. EV_PWR is fine for telling input devices
to do something, like enter lower power mode and for sending _some_
requests to the PM system. But input layer shoudl not be used as a
generic transport. I mean battery low, docking requests, etc has
nothing to do with input.
--
Dmitry
next prev parent reply other threads:[~2005-02-18 18:19 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 0:47 2.6: drivers/input/power.c is never built Adrian Bunk
2005-02-14 18:04 ` James Simmons
2005-02-14 19:34 ` Vojtech Pavlik
2005-02-18 12:22 ` Pavel Machek
2005-02-18 13:10 ` Richard Purdie
2005-02-18 13:26 ` Pavel Machek
2005-02-18 13:36 ` Oliver Neukum
2005-02-18 16:01 ` Pavel Machek
2005-02-18 17:00 ` Vojtech Pavlik
2005-02-18 17:05 ` Oliver Neukum
2005-02-18 17:48 ` Vojtech Pavlik
2005-02-18 21:32 ` James Simmons
2005-02-18 20:14 ` Pavel Machek
2005-02-18 20:39 ` Oliver Neukum
2005-02-18 18:19 ` Dmitry Torokhov [this message]
2005-02-18 18:39 ` Vojtech Pavlik
2005-02-18 19:20 ` Dmitry Torokhov
2005-02-18 20:05 ` Vojtech Pavlik
2005-02-18 20:24 ` Pavel Machek
2005-02-18 20:40 ` Vojtech Pavlik
2005-02-18 20:59 ` Pavel Machek
2005-02-18 21:23 ` Oliver Neukum
2005-02-18 21:34 ` Pavel Machek
2005-02-18 22:00 ` Oliver Neukum
2005-02-18 23:34 ` Pavel Machek
2005-02-18 23:51 ` Oliver Neukum
2005-02-19 0:13 ` Pavel Machek
2005-02-19 1:16 ` Xavier Bestel
2005-02-18 21:38 ` Vojtech Pavlik
2005-02-18 23:31 ` Pavel Machek
2005-02-19 2:58 ` Dmitry Torokhov
2005-02-19 6:28 ` Nigel Cunningham
2005-02-19 6:53 ` Dmitry Torokhov
2005-02-19 9:10 ` Nigel Cunningham
2005-02-21 18:11 ` James Simmons
2005-02-21 18:34 ` Wichert Akkerman
2005-02-21 21:37 ` James Simmons
2005-02-21 22:50 ` Nigel Cunningham
2005-02-21 22:52 ` James Simmons
2005-02-21 22:57 ` Wichert Akkerman
2005-02-21 22:54 ` Wichert Akkerman
2005-02-19 20:29 ` Pavel Machek
2005-02-19 20:31 ` Pavel Machek
2005-02-21 18:19 ` James Simmons
2005-02-18 14:02 ` Richard Purdie
2005-02-18 14:12 ` Dmitry Torokhov
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=d120d50005021810195f16ac0d@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=bunk@stusta.de \
--cc=dtor_core@ameritech.net \
--cc=jsimmons@pentafluge.infradead.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=pavel@suse.cz \
--cc=rpurdie@rpsys.net \
--cc=vojtech@suse.cz \
/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