From: Carlos Corbacho <carlos@strangeworlds.co.uk>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] acpi-wmi: Enable event methods when registering notifiers
Date: Wed, 27 Aug 2008 22:15:09 +0100 [thread overview]
Message-ID: <200808272215.10199.carlos@strangeworlds.co.uk> (raw)
In-Reply-To: <20080827150401.GA8966@srcf.ucam.org>
On Wednesday 27 August 2008 16:04:01 Matthew Garrett wrote:
> According to the ACPI-WMI spec, event blocks may provide a function call
> for enabling/disabling them. This patch adds support for making these
> calls when registering or removing notifications. Without this, my Dell
> firmware provides no data in the event notification.
>
> Signed-off-by: Matthew Garrett <mjg@redhat.com>
Signed-off-by: Carlos Corbacho <carlos@strangeworlds.co.uk>
Andi, can you take this into the ACPI tree?
>
> ---
>
> diff --git a/drivers/acpi/wmi.c b/drivers/acpi/wmi.c
> index c33b1c6..c7f735f 100644
> --- a/drivers/acpi/wmi.c
> +++ b/drivers/acpi/wmi.c
> @@ -217,6 +217,35 @@ static bool find_guid(const char *guid_string, struct
> wmi_block **out) return 0;
> }
>
> +static acpi_status wmi_method_enable(struct wmi_block *wblock, int enable)
> +{
> + struct guid_block *block = NULL;
> + char method[5];
> + struct acpi_object_list input;
> + union acpi_object params[1];
> + acpi_status status;
> + acpi_handle handle;
> +
> + block = &wblock->gblock;
> + handle = wblock->handle;
> +
> + if (!block)
> + return AE_NOT_EXIST;
> +
> + input.count = 1;
> + input.pointer = params;
> + params[0].type = ACPI_TYPE_INTEGER;
> + params[0].integer.value = enable;
> +
> + snprintf(method, 5, "WE%02X", block->notify_id);
> + status = acpi_evaluate_object(handle, method, &input, NULL);
> +
> + if (status != AE_OK && status != AE_NOT_FOUND)
> + return status;
> + else
> + return AE_OK;
> +}
> +
> /*
> * Exported WMI functions
> */
> @@ -427,6 +456,7 @@ acpi_status wmi_install_notify_handler(const char
> *guid, wmi_notify_handler handler, void *data)
> {
> struct wmi_block *block;
> + acpi_status status;
>
> if (!guid || !handler)
> return AE_BAD_PARAMETER;
> @@ -441,7 +471,9 @@ wmi_notify_handler handler, void *data)
> block->handler = handler;
> block->handler_data = data;
>
> - return AE_OK;
> + status = wmi_method_enable(block, 1);
> +
> + return status;
> }
> EXPORT_SYMBOL_GPL(wmi_install_notify_handler);
>
> @@ -453,6 +485,7 @@ EXPORT_SYMBOL_GPL(wmi_install_notify_handler);
> acpi_status wmi_remove_notify_handler(const char *guid)
> {
> struct wmi_block *block;
> + acpi_status status;
>
> if (!guid)
> return AE_BAD_PARAMETER;
> @@ -464,10 +497,12 @@ acpi_status wmi_remove_notify_handler(const char
> *guid) if (!block->handler)
> return AE_NULL_ENTRY;
>
> + status = wmi_method_enable(block, 0);
> +
> block->handler = NULL;
> block->handler_data = NULL;
>
> - return AE_OK;
> + return status;
> }
> EXPORT_SYMBOL_GPL(wmi_remove_notify_handler);
--
E-Mail: carlos@strangeworlds.co.uk
Web: strangeworlds.co.uk
GPG Key ID: 0x23EE722D
prev parent reply other threads:[~2008-08-27 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 15:04 [PATCH] acpi-wmi: Enable event methods when registering notifiers Matthew Garrett
2008-08-27 21:15 ` Carlos Corbacho [this message]
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=200808272215.10199.carlos@strangeworlds.co.uk \
--to=carlos@strangeworlds.co.uk \
--cc=ak@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox