From: Jukka Ruohonen <jruohonen at iki.fi>
To: devel@acpica.org
Subject: Re: [Devel] AcpiClearGpe() and recent changes
Date: Thu, 10 Jun 2010 23:23:03 +0300 [thread overview]
Message-ID: <20100610202303.GA5424@marx.bitnet> (raw)
In-Reply-To: 4911F71203A09E4D9981D27F9D83085870DEC8AD@orsmsx503.amr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
On Thu, Jun 10, 2010 at 01:09:38PM -0700, Moore, Robert wrote:
> I'm not entirely sure at the moment, but we are about to make some
> additional GPE changes since some issues with the reference count
> mechanism have been uncovered.
>
> Do you have a need to call AcpiClearGpe from interrupt level?
No.
I was mainly after the inconsistency in the API. As AcpiClearGpe() uses
unconditionally the same lock that has been acquired earlier by one of the
dispatching functions, this leads to a panic or other comparable condition,
depending on the implementation.
So perhaps this could be solved at the documentation level by nothing that
AcpiClearGpe() may NOT be used from a GPE handler.
- Jukka.
next reply other threads:[~2010-06-10 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 20:23 Jukka Ruohonen [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-10 20:09 [Devel] AcpiClearGpe() and recent changes Moore, Robert
2010-06-06 9:17 Jukka Ruohonen
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=20100610202303.GA5424@marx.bitnet \
--to=devel@acpica.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 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.