mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'Patrick Mochel'" <mochel@osdl.org>
Cc: "'Mario 'BitKoenig' Holbe'" <Mario.Holbe@RZ.TU-Ilmenau.DE>,
	Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org
Subject: RE: [patch] ACPI: kbd-pw-on/WOL don't work anymore since 2.4.14
Date: Tue, 12 Mar 2002 13:51:57 -0800	[thread overview]
Message-ID: <59885C5E3098D511AD690002A5072D3C02AB7CDD@orsmsx111.jf.intel.com> (raw)

> From: Patrick Mochel [mailto:mochel@osdl.org]
> It seems like this would ideally be specified in the config 
> file for the 
> power management agent. So, before the transition to sleep began, the 
> agent would enable those devices to wake the system (probably 
> by writing a 
> value to a driverfs file). 

Agree.

> The only thing is that you probably want all devices of a 
> particular class 
> to wake a system - like all keyboards or all net devices. I 
> don't know 
> what the config file format for ospmd looks like, but it 
> might articulated 
> like:
> 
> /* devices to wake the system when we go to sleep */
> wake {
> 	keyboard
> 	network
> 	mouse
> }
> Right?

Sounds OK to me. Once the wake capability and class of a device are both
visible through driverfs, implementing functionality like this in userspace
is easy.

Regards -- Andy

             reply	other threads:[~2002-03-12 21:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-12 21:51 Grover, Andrew [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-12 23:05 Grover, Andrew
2002-03-12 23:13 ` Mario 'BitKoenig' Holbe
2002-03-12 19:57 Grover, Andrew
2002-03-12 20:40 ` Patrick Mochel
2002-03-12 22:38 ` Mario 'BitKoenig' Holbe
2002-03-10 18:05 Mario 'BitKoenig' Holbe
2002-03-11 20:34 ` Pavel Machek
2002-03-12 15:08   ` Mario 'BitKoenig' Holbe

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=59885C5E3098D511AD690002A5072D3C02AB7CDD@orsmsx111.jf.intel.com \
    --to=andrew.grover@intel.com \
    --cc=Mario.Holbe@RZ.TU-Ilmenau.DE \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=pavel@ucw.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

all inboxes | Powered by JetHome®