public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
To: "Li, Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: acpi_enable_wakeup_device question
Date: Mon, 23 Aug 2004 13:12:55 -0500	[thread overview]
Message-ID: <200408231312.59209.dtor_core@ameritech.net> (raw)
In-Reply-To: <B44D37711ED29844BEA67908EAF36F039EA6FA-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>

On Monday 23 August 2004 01:29 am, Li, Shaohua wrote:
> Hi,
> Please look at the P212 in 2.0a or P215 in 2.0c(_PRW method). The reason
> is ACPI recommend disabling interrupt, please look at the example at the
> end of the section. Yes, enabling interrupt possibly doesn't matter (my
> test shows it works), but we don't know if it works for all systems, so
> we just obey to spec.
> 

Thank you for pointing the exact place in the spec, although I do not
agree with your reading of it. I think it says that before entering the
sleep state all 3 conditions should be satisfied, but it does not
necessarily specifies the order in which the actions should be performed.
For example checking the validity of requested sleep state in no way
relies on interupts being disabled as _PRW is required to return the same
information every time it is invoked and as far as I can see Linux ACPI
implementation only executes it at device scan.

I think that it is safe to move acpi_enable_wakeup_device up a bit;
having interrupts disabled when entering sleep state is completely
reasonable though.

-- 
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

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-23  6:18 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=200408231312.59209.dtor_core@ameritech.net \
    --to=dtor_core-ywtbtysyrb+lz21kgmrzwg@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@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