From: Dmitry Torokhov <dtor_core@ameritech.net>
To: ncunningham@cyclades.com
Cc: Pavel Machek <pavel@suse.cz>, Vojtech Pavlik <vojtech@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: Sat, 19 Feb 2005 01:53:11 -0500 [thread overview]
Message-ID: <200502190153.12535.dtor_core@ameritech.net> (raw)
In-Reply-To: <1108794519.4098.24.camel@desktop.cunningham.myip.net.au>
Hi Nigel,
On Saturday 19 February 2005 01:28, Nigel Cunningham wrote:
> Hi.
>
> On Sat, 2005-02-19 at 13:58, Dmitry Torokhov wrote:
> > On Friday 18 February 2005 18:31, Pavel Machek wrote:
> > > I believe power and suspend keys should definitely go through
> > > input. I'm not that sure about battery... Lid is somewhere in
> > > between...
> > I think we need a generic way of delivering system status changes to
> > userspace. Something like acpid but bigger than that, something not
> > so heavily oriented on ACPI. I wonder if that kernel connector patch
> > should be looked at.
>
> Absolutely. I've been thinking about this too, but haven't yet found the
> time to put it down on paper/email yet.
>
> I think we need a very generic system by which changes in anything
> remotely impacting on power management (kernelspace or userspace,
> including ACPI, UPS drivers, keyboard handlers, devices etc) can notify
> events to a userspace daemon. This daemon can act in accordance with
> user specified policies (changeable on the fly) to implement system
> level state changes (suspend to ram/disk, shutdown etc), run time power
> management
Yep.
> (shutdown a USB hub that just signalled the removal of its
> last client), logging and so on.
This last example - I don't think the daemon should micro-manage, I think
USB bus should shutdown the hub automatically without involving userspace.
> In some cases, it might set policy but
> not be actively informed of the details of the application of that
> policy (we don't feedback loops with a process leaving C3 to notify that
> it's entering C3!).
>
> This implies, of course, not just a generic way of notifying changes,
> but a generic way of implementing policy.
>
> Sound too ambitious, or am I thinking your thoughts after you?
>
Well, at this moment I only care about delivering the data to userspace,
the rest (daemon, policies) is although interesting is out of scope for
me.
--
Dmitry
next prev parent reply other threads:[~2005-02-19 6:53 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
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 [this message]
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=200502190153.12535.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=bunk@stusta.de \
--cc=jsimmons@pentafluge.infradead.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
--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 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.