public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Perkins <bperkins-ooduxAEi7gVg9hUCZPvPmw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: wake event?
Date: Thu, 11 Dec 2003 21:18:03 -0500	[thread overview]
Message-ID: <3FD9255B.4030107@netspace.org> (raw)

I've started playing around with the acpid socket for writing power
management clients.

One deficiency that I've noticed is that events don't arrive while the 
machine is sleeping (not too surprising).  This means that things like 
ac status monitors will be incorrect if the ac status changes while we 
are sleeping.

It might be nice to deliver a wake event to /proc/acpi/event so clients
can know that they can update properly.

I thought about writing a patch to do this, but I had trouble deciding
what arguments ought to be given to acpi_bus_generate_event (device 
e.g.), and where it should be done.  Perhaps this is because this 
feature is somewhat outside the scope of what was originally intended 
the interface.

Any thoughts?

--
Brian Perkins				bperkins-5L9LcNmrgCtAfugRpC6u6w@public.gmane.org




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

             reply	other threads:[~2003-12-12  2:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12  2:18 Brian Perkins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-12  3:01 wake event? Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C24-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-12  3:26   ` Brian Perkins
2003-12-16  9:30 Yu, Luming

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=3FD9255B.4030107@netspace.org \
    --to=bperkins-ooduxaei7gvg9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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