public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J . Wysocki " <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, Ferry Toth <fntoth@gmail.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v1] ACPI / platform: Unregister stale platform devices
Date: Thu, 17 Oct 2019 14:38:47 +0300	[thread overview]
Message-ID: <20191017113847.GM32742@smile.fi.intel.com> (raw)
In-Reply-To: <20190830143432.21695-1-andriy.shevchenko@linux.intel.com>

On Fri, Aug 30, 2019 at 05:34:32PM +0300, Andy Shevchenko wrote:
> When the commit 68bdb6773289
> 
>   ("ACPI: add support for ACPI reconfiguration notifiers")
> 
> introduced reconfiguration notifiers it misses the point that the ACPI table,
> which may be loaded and then unloaded via ConfigFS, can contain devices that are
> not enumerated by their parents.
> 
> In such case the stale platform device is dangling in the system while the rest
> of the devices from the same table are already gone.
> 
> Introduce acpi_platform_device_remove_notify() notifier that, in similar way to
> I²C or SPI buses, unregisters the platform devices on table removal event.
> 

Rafael, all dependencies now in v5.4-rc1.
Can this be applied, or I need to do more work?

> Depends-on: 00500147cbd3 ("drivers: Introduce device lookup variants by ACPI_COMPANION device")
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  drivers/acpi/acpi_platform.c | 43 ++++++++++++++++++++++++++++++++++++
>  drivers/acpi/scan.c          |  1 +
>  2 files changed, 44 insertions(+)
> 
> diff --git a/drivers/acpi/acpi_platform.c b/drivers/acpi/acpi_platform.c
> index 00ec4f2bf015..dfcd6210828e 100644
> --- a/drivers/acpi/acpi_platform.c
> +++ b/drivers/acpi/acpi_platform.c
> @@ -31,6 +31,44 @@ static const struct acpi_device_id forbidden_id_list[] = {
>  	{"", 0},
>  };
>  
> +static struct platform_device *acpi_platform_device_find_by_adev(struct acpi_device *adev)
> +{
> +	struct device *dev;
> +
> +	dev = bus_find_device_by_acpi_dev(&platform_bus_type, adev);
> +	return dev ? to_platform_device(dev) : NULL;
> +}
> +
> +static int acpi_platform_device_remove_notify(struct notifier_block *nb,
> +					      unsigned long value, void *arg)
> +{
> +	struct acpi_device *adev = arg;
> +	struct platform_device *pdev;
> +
> +	switch (value) {
> +	case ACPI_RECONFIG_DEVICE_ADD:
> +		/* Nothing to do here */
> +		break;
> +	case ACPI_RECONFIG_DEVICE_REMOVE:
> +		if (!acpi_device_enumerated(adev))
> +			break;
> +
> +		pdev = acpi_platform_device_find_by_adev(adev);
> +		if (!pdev)
> +			break;
> +
> +		platform_device_unregister(pdev);
> +		put_device(&pdev->dev);
> +		break;
> +	}
> +
> +	return NOTIFY_OK;
> +}
> +
> +static struct notifier_block acpi_platform_notifier = {
> +	.notifier_call = acpi_platform_device_remove_notify,
> +};
> +
>  static void acpi_platform_fill_resource(struct acpi_device *adev,
>  	const struct resource *src, struct resource *dest)
>  {
> @@ -130,3 +168,8 @@ struct platform_device *acpi_create_platform_device(struct acpi_device *adev,
>  	return pdev;
>  }
>  EXPORT_SYMBOL_GPL(acpi_create_platform_device);
> +
> +void __init acpi_platform_init(void)
> +{
> +	acpi_reconfig_notifier_register(&acpi_platform_notifier);
> +}
> diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
> index aad6be5c0af0..915650bf519f 100644
> --- a/drivers/acpi/scan.c
> +++ b/drivers/acpi/scan.c
> @@ -2174,6 +2174,7 @@ int __init acpi_scan_init(void)
>  	acpi_pci_root_init();
>  	acpi_pci_link_init();
>  	acpi_processor_init();
> +	acpi_platform_init();
>  	acpi_lpss_init();
>  	acpi_apd_init();
>  	acpi_cmos_rtc_init();
> -- 
> 2.23.0.rc1
> 

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2019-10-17 11:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 14:34 [PATCH v1] ACPI / platform: Unregister stale platform devices Andy Shevchenko
2019-09-02  6:38 ` kbuild test robot
2019-09-02  9:52   ` Andy Shevchenko
2019-09-04  8:46     ` [kbuild-all] " Rong Chen
2019-09-02  7:19 ` kbuild test robot
2019-09-02  9:55   ` Andy Shevchenko
2019-10-17 11:38 ` Andy Shevchenko [this message]
2019-10-17 21:57 ` Rafael J. Wysocki
2019-10-18  8:35   ` Andy Shevchenko

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=20191017113847.GM32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=fntoth@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    /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