From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Len Brown <lenb@kernel.org>, Bob Moore <robert.moore@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 4/6] ACPICA: Implicit notify support
Date: Thu, 9 Dec 2010 23:30:43 +0100 [thread overview]
Message-ID: <201012092330.43478.rjw@sisk.pl> (raw)
In-Reply-To: <1291651138.2197.86.camel@localhost>
On Monday, December 06, 2010, Lin Ming wrote:
> This feature provides an automatic device notification for wake devices
> when a wakeup GPE occurs and there is no corresponding GPE method or
> handler. Rather than ignoring such a GPE, an implicit AML Notify
> operation is performed on the parent device object.
> This feature is not part of the ACPI specification and is provided for
> Windows compatibility only.
>
> Signed-off-by: Lin Ming <ming.m.lin@intel.com>
This patch does two things at a time, while only one is mentioned in the
changelog. The second one is that you change the local variable in
acpi_ev_asynch_execute_gpe_method() back into a pointer:
...
>
> static void ACPI_SYSTEM_XFACE acpi_ev_asynch_execute_gpe_method(void *context)
> {
> - struct acpi_gpe_event_info *gpe_event_info = (void *)context;
> + struct acpi_gpe_event_info *gpe_event_info = context;
> acpi_status status;
> - struct acpi_gpe_event_info local_gpe_event_info;
> + struct acpi_gpe_event_info *local_gpe_event_info;
> struct acpi_evaluate_info *info;
>
> ACPI_FUNCTION_TRACE(ev_asynch_execute_gpe_method);
>
> + /* Allocate a local GPE block */
> +
> + local_gpe_event_info =
> + ACPI_ALLOCATE_ZEROED(sizeof(struct acpi_gpe_event_info));
> + if (!local_gpe_event_info) {
> + ACPI_EXCEPTION((AE_INFO, AE_NO_MEMORY, "while handling a GPE"));
> + return_VOID;
> + }
> +
> status = acpi_ut_acquire_mutex(ACPI_MTX_EVENTS);
> if (ACPI_FAILURE(status)) {
> return_VOID;
> @@ -468,7 +479,7 @@ static void ACPI_SYSTEM_XFACE acpi_ev_asynch_execute_gpe_method(void *context)
> * Take a snapshot of the GPE info for this level - we copy the info to
> * prevent a race condition with remove_handler/remove_block.
> */
> - ACPI_MEMCPY(&local_gpe_event_info, gpe_event_info,
> + ACPI_MEMCPY(local_gpe_event_info, gpe_event_info,
> sizeof(struct acpi_gpe_event_info));
>
etc. and that should go into a separate patch.
I mean, first fix this local variable mess and _then_ introdiuce the new
feature. Doing both in one step is guaranteed to confuse people.
Thanks,
Rafael
next prev parent reply other threads:[~2010-12-09 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 15:58 [PATCH 4/6] ACPICA: Implicit notify support Lin Ming
2010-12-09 22:30 ` Rafael J. Wysocki [this message]
2010-12-10 0:18 ` Lin Ming
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=201012092330.43478.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.com \
/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