From: Andriy Gapon <avg at FreeBSD.org>
To: devel@acpica.org
Subject: Re: [Devel] AcpiGetEventStatus: interface with behavior
Date: Fri, 25 Jan 2013 10:22:59 +0200 [thread overview]
Message-ID: <510240E3.8060603@FreeBSD.org> (raw)
In-Reply-To: 50DAB867.4050402@FreeBSD.org
[-- 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
next reply other threads:[~2013-01-25 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 8:22 Andriy Gapon [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-26 8:42 [Devel] AcpiGetEventStatus: interface with behavior Andriy Gapon
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=510240E3.8060603@FreeBSD.org \
--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.