From: Al Stone <ahs3 at redhat.com>
To: devel@acpica.org
Subject: Re: [Devel] GPE blocks in reduced hardware mode
Date: Tue, 03 Dec 2013 18:39:16 -0700 [thread overview]
Message-ID: <529E87C4.7020307@redhat.com> (raw)
In-Reply-To: 94F2FBAB4432B54E8AACC7DFDE6C92E37C7A5FD1@ORSMSX103.amr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 2687 bytes --]
On 12/03/2013 05:18 PM, Moore, Robert wrote:
> The first thing is that there are no GPE block devices in the field, never have been. I don't think ACPICA actually supports them fully. It is a bit of an "orphan" feature of ACPI.
I see. Yeah, I did find GPE block device support confusing in the
code. It seems like the infrastructure to handle them is present,
but there is no code to handle the "ACPI0006" ID anywhere I can find
(that may be a Linux limitation, though).
> I'll have to take a look closer at the spec for an exact reference, but basically one of the things that ACPI_REDUCED_HARDWARE means is no GPEs, IIRC.
Right -- that's what ACPI_REDUCED_HARDWARE means in the ACPICA code;
that seems pretty clear. I just can't seem to find anything that clear
in the spec :/...
I'll continue to look in the spec but if you find something before I
do, do let me know.
Thanks!
>> -----Original Message-----
>> From: Devel [mailto:devel-bounces(a)acpica.org] On Behalf Of Al Stone
>> Sent: Tuesday, December 03, 2013 2:38 PM
>> To: devel(a)acpica.org
>> Subject: [Devel] GPE blocks in reduced hardware mode
>>
>> Howdy.
>>
>> I've been trying to do some clean-up on the Linux ACPI driver with regard
>> to the reduced hardware profile introduced in ACPI 5.0.
>>
>> In thinking about GPE block devices, I was looking through the functions
>> in source/components/events/evxfgpe.c and noticed that they are all
>> #ifdef'd out for ACPI_REDUCED_HARDWARE. When I look back through the
>> specification, however, I cannot find any place where they are prohibited.
>>
>> Clearly, the gpe0/1 blocks in the FADT are not to be used; this is
>> explicitly stated in section 5.2.9 of the spec. Could someone please
>> point me to a similar statement for a GPE block device? I just cannot
>> seem to find it.
>>
>> The closest thing I can find is section 9.10 implying that a GPE block
>> device is an extension of the gpe0/1 blocks from the FADT, but there is no
>> explicit statement there so it is ambiguous to me.
>>
>> Thanks in advance for any pointers; I'm just puzzled at this point and
>> trying to understand how the conclusion came to be.
>>
>> --
>> ciao,
>> al
>> -----------------------------------
>> Al Stone
>> Software Engineer
>> Red Hat, Inc.
>> ahs3(a)redhat.com
>> -----------------------------------
>> _______________________________________________
>> Devel mailing list
>> Devel(a)acpica.org
>> https://lists.acpica.org/mailman/listinfo/devel
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3(a)redhat.com
-----------------------------------
next reply other threads:[~2013-12-04 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 1:39 Al Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-05 16:25 [Devel] GPE blocks in reduced hardware mode Moore, Robert
2013-12-05 16:23 Al Stone
2013-12-04 15:51 Moore, Robert
2013-12-04 6:28 Moore, Robert
2013-12-04 0:18 Moore, Robert
2013-12-03 22:38 Al Stone
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=529E87C4.7020307@redhat.com \
--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.