From: "Richard Purdie" <rpurdie@rpsys.net>
To: "Pavel Machek" <pavel@suse.cz>,
"Vojtech Pavlik" <vojtech@suse.cz>,
"James Simmons" <jsimmons@pentafluge.infradead.org>,
"Adrian Bunk" <bunk@stusta.de>
Cc: "Linux Input Devices" <linux-input@atrey.karlin.mff.cuni.cz>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
<dmitry.torokhov@gmail.com>
Subject: Re: 2.6: drivers/input/power.c is never built
Date: Fri, 18 Feb 2005 13:10:43 -0000 [thread overview]
Message-ID: <047401c515bb$437b5130$0f01a8c0@max> (raw)
In-Reply-To: 20050218122217.GA1523@elf.ucw.cz
> > > In 2.6, drivers/input/power.c would only have been built if
> > > CONFIG_INPUT_POWER was enabled - but it is nowhere possible to enable
> > > this option.
> >
> > That was written a long time ago before the new power management went
> > in.
> > On PDA's there is a power button and suspend button. So this was a hook
> > so that the input layer could detect the power/suspend button being
> > presses and then power down or turn off the device. Now that the new
> > power
> > management is in what should we do?
>
> Change power.c to generate power events like ACPI does, most likely.
There was some recent discussion of this on linux-input. It was basically
agreed that the input system should pass the request on to ACPI and/or apm
and Dmitry Torokhov (cc'd) proposed a patch that did this. His patch needed
to be slightly modified to work with arm apm, the final result being:
http://www.rpsys.net/openzaurus/2.6.11-rc4/input_power-r1.patch
I can confirm this works well on arm with apm enabled.
Regards,
Richard
next prev parent reply other threads:[~2005-02-18 13:14 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 [this message]
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
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='047401c515bb$437b5130$0f01a8c0@max' \
--to=rpurdie@rpsys.net \
--cc=bunk@stusta.de \
--cc=dmitry.torokhov@gmail.com \
--cc=jsimmons@pentafluge.infradead.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.