From: Armin Wolf <W_Armin@gmx.de>
To: hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2 2/6] platform/x86: wmi: Remove ACPI handlers after WMI devices
Date: Mon, 18 Dec 2023 21:34:50 +0100 [thread overview]
Message-ID: <6f4de52e-2aff-4f56-8407-e9caf81d4a54@gmx.de> (raw)
In-Reply-To: <20231218201844.2860-3-W_Armin@gmx.de>
Am 18.12.23 um 21:18 schrieb Armin Wolf:
> When removing the ACPI notify/address space handlers, the WMI devices
> are still active and might still depend on ACPI EC access or
> WMI events.
> Fix this by removing the ACPI handlers after all WMI devices
> associated with an ACPI device have been removed.
Sorry for sending the patch series multiple times, it seems my mail provider has
some kind of issue which prevents me from receiving mail from this list (this is
the only patch i received from my series so far). Because this i thought that my
patch series got lost somehow.
Armin Wolf
>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
> ---
> drivers/platform/x86/wmi.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/platform/x86/wmi.c b/drivers/platform/x86/wmi.c
> index 906d3a2831ae..2120c13e1676 100644
> --- a/drivers/platform/x86/wmi.c
> +++ b/drivers/platform/x86/wmi.c
> @@ -1239,13 +1239,12 @@ static void acpi_wmi_remove(struct platform_device *device)
> struct acpi_device *acpi_device = ACPI_COMPANION(&device->dev);
> struct device *wmi_bus_device = dev_get_drvdata(&device->dev);
>
> - acpi_remove_notify_handler(acpi_device->handle, ACPI_ALL_NOTIFY,
> - acpi_wmi_notify_handler);
> - acpi_remove_address_space_handler(acpi_device->handle,
> - ACPI_ADR_SPACE_EC, &acpi_wmi_ec_space_handler);
> -
> device_for_each_child_reverse(wmi_bus_device, NULL, wmi_remove_device);
> device_unregister(wmi_bus_device);
> +
> + acpi_remove_notify_handler(acpi_device->handle, ACPI_ALL_NOTIFY, acpi_wmi_notify_handler);
> + acpi_remove_address_space_handler(acpi_device->handle, ACPI_ADR_SPACE_EC,
> + &acpi_wmi_ec_space_handler);
> }
>
> static int acpi_wmi_probe(struct platform_device *device)
> --
> 2.39.2
>
>
next prev parent reply other threads:[~2023-12-18 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 20:18 [PATCH RESEND v2 0/6] platform/x86: wmi: ACPI improvements Armin Wolf
2023-12-18 20:18 ` [PATCH RESEND v2 1/6] platform/x86: wmi: Remove unused variable in address space handler Armin Wolf
2023-12-18 20:18 ` [PATCH RESEND v2 2/6] platform/x86: wmi: Remove ACPI handlers after WMI devices Armin Wolf
2023-12-18 20:34 ` Armin Wolf [this message]
2023-12-18 20:18 ` [PATCH RESEND v2 3/6] platform/x86: wmi: Use devres for resource handling Armin Wolf
2023-12-18 20:18 ` [PATCH RESEND v2 4/6] platform/x86: wmi: Create WMI bus device first Armin Wolf
2023-12-18 20:18 ` [PATCH RESEND v2 5/6] platform/x86: wmi: Decouple ACPI notify handler from wmi_block_list Armin Wolf
2023-12-18 20:18 ` [PATCH RESEND v2 6/6] platform/x86: wmi: Simplify get_subobj_info() Armin Wolf
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=6f4de52e-2aff-4f56-8407-e9caf81d4a54@gmx.de \
--to=w_armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.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