All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>,
	Linux PCI <linux-pci@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 0/3] PCI: ACPI: glue: Get rid of acpi_pci_bus and rearrange code
Date: Sat, 18 Sep 2021 14:51:24 +0200	[thread overview]
Message-ID: <1794818.tdWV9SEqCh@kreacher> (raw)

Hi All,

After commit 375553a93201 ("PCI: Setup ACPI fwnode early and at the same time
with OF"), PCI only uses acpi_pci_bus for running the ->setup() and ->cleanup()
callbacks from there, but the functions pointed to by them can be invoked
directly from the ACPI "glue" code if the device being processed is a PCI one,
so patch [1/3] drops acpi_pci_bus and rearranges the code to call the PCI
"setup" and "cleanup" routines directly.

After that, the ->cleanup callback in struct acpi_bus_type has no users, so
patch [2/3] gets rid of it.

Finally, patch [3/3] rearranges acpi_device_notify() to avoid looking up
the "ACPI bus type" of the device in bus_type_list if its ACPI companion has
been set upfront.

Thanks!




             reply	other threads:[~2021-09-18 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 12:51 Rafael J. Wysocki [this message]
2021-09-18 12:53 ` [PATCH v1 1/3] PCI: ACPI: Drop acpi_pci_bus Rafael J. Wysocki
2021-09-18 12:56 ` [PATCH v1 2/3] ACPI: glue: Drop cleanup callback from struct acpi_bus_type Rafael J. Wysocki
2021-09-18 13:02 ` [PATCH v1 3/3] ACPI: glue: Look for ACPI bus type only if ACPI companion is not known Rafael J. Wysocki

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=1794818.tdWV9SEqCh@kreacher \
    --to=rjw@rjwysocki.net \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=helgaas@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.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 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.