* [Devel] AcpiGetEventStatus: interface with behavior
@ 2012-12-26 8:42 Andriy Gapon
0 siblings, 0 replies; 2+ messages in thread
From: Andriy Gapon @ 2012-12-26 8:42 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
AcpiGetEventStatus has an out parameter of type ACPI_EVENT_STATUS.
My impression that values of that type should conform to bit definitions
provided near the type declaration (ACPI_EVENT_FLAG_ENABLED,
ACPI_EVENT_FLAG_SET, etc).
But it seems that currently AcpiGetEventStatus returns only values zero and one
corresponding to inactive and active status.
The linux (adaption of the) code here
http://lxr.linux.no/#linux+v3.7.1/drivers/acpi/acpica/evxfevnt.c#L313
seems to be a bit more elaborate. It actually tries to produce a value that
conforms to the definitions by examining not only the status register but also
enable register.
It looks like AcpiHwGetGpeStatus is the model for how ACPI_EVENT_STATUS should
be populated. I am not sure if AcpiGetEventStatus should be made compatible
with ACPI_EVENT_STATUS or if its out type should be changed to something else.
Also, it looks that the comment near ACPI_EVENT_STATUS definitions is a little
bit out of sync.
--
Andriy Gapon
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Devel] AcpiGetEventStatus: interface with behavior
@ 2013-01-25 8:22 Andriy Gapon
0 siblings, 0 replies; 2+ messages in thread
From: Andriy Gapon @ 2013-01-25 8:22 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
[ping]
on 26/12/2012 10:42 Andriy Gapon said the following:
>
> AcpiGetEventStatus has an out parameter of type ACPI_EVENT_STATUS.
> My impression that values of that type should conform to bit definitions
> provided near the type declaration (ACPI_EVENT_FLAG_ENABLED,
> ACPI_EVENT_FLAG_SET, etc).
> But it seems that currently AcpiGetEventStatus returns only values zero and one
> corresponding to inactive and active status.
>
> The linux (adaption of the) code here
> http://lxr.linux.no/#linux+v3.7.1/drivers/acpi/acpica/evxfevnt.c#L313
> seems to be a bit more elaborate. It actually tries to produce a value that
> conforms to the definitions by examining not only the status register but also
> enable register.
>
> It looks like AcpiHwGetGpeStatus is the model for how ACPI_EVENT_STATUS should
> be populated. I am not sure if AcpiGetEventStatus should be made compatible
> with ACPI_EVENT_STATUS or if its out type should be changed to something else.
>
> Also, it looks that the comment near ACPI_EVENT_STATUS definitions is a little
> bit out of sync.
>
--
Andriy Gapon
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-01-25 8:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-26 8:42 [Devel] AcpiGetEventStatus: interface with behavior Andriy Gapon
-- strict thread matches above, loose matches on Subject: below --
2013-01-25 8:22 Andriy Gapon
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.