public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: acpi_enable_wakeup_device question
Date: Mon, 23 Aug 2004 01:18:53 -0500	[thread overview]
Message-ID: <200408230118.53301.dtor_core@ameritech.net> (raw)

Hi,

I see the following comment in drivers/acpi/sleeip/wakeup.c:

/**
 * acpi_enable_wakeup_device - enable wakeup devices
 *      @sleep_state:   ACPI state
 * Enable all wakup devices's GPE
 */
void
acpi_enable_wakeup_device(
        u8              sleep_state)
{
        struct list_head * node, * next;


        /*
         * Caution: this routine must be invoked when interrupt is disabled
         * Refer ACPI2.0: P212
         */

But I can not seem to find anything related to that on p.212 ACPI 2.0c.
As far as I can tell functions called by acpi_enable_wakeup_device (such
as acpi_set_gpe_type and acpi_enable_gpe) can be safely called from
process context. Why this function has to be called with interrupts
disabled?

Thanks!

-- 
Dmitry


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

             reply	other threads:[~2004-08-23  6:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23  6:18 Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-23  6:29 acpi_enable_wakeup_device question Li, Shaohua
     [not found] ` <B44D37711ED29844BEA67908EAF36F039EA6FA-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-23 18: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=200408230118.53301.dtor_core@ameritech.net \
    --to=dtor_core-ywtbtysyrb+lz21kgmrzwg@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