From: Bjorn Helgaas <helgaas@kernel.org>
To: Vidya Sagar <vidyas@nvidia.com>
Cc: bhelgaas@google.com, rafael@kernel.org, lenb@kernel.org,
will@kernel.org, lpieralisi@kernel.org, kw@linux.com,
robh@kernel.org, frowand.list@gmail.com,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
treding@nvidia.com, jonathanh@nvidia.com, kthota@nvidia.com,
mmaddireddy@nvidia.com, sagar.tv@gmail.com
Subject: Re: [PATCH V7 0/4] PCI: Add support for preserving boot configuration
Date: Mon, 3 Jun 2024 16:21:46 -0500 [thread overview]
Message-ID: <20240603212146.GA697762@bhelgaas> (raw)
In-Reply-To: <20240508174138.3630283-1-vidyas@nvidia.com>
On Wed, May 08, 2024 at 11:11:34PM +0530, Vidya Sagar wrote:
> Add support for preserving the boot configuration done by the
> platform firmware per host bridge basis, based on the presence of
> 'linux,pci-probe-only' property in the respective PCI host bridge
> device-tree node. It also unifies the ACPI and DT based boot flows
> in this regard.
>
> This patch series is a complete version of the incomplete series
> ( https://lore.kernel.org/linux-pci/20240421190914.374399-1-helgaas@kernel.org/ )
> posted by Bjorn which in turn was an attempted split work of the single V6 patch
> ( https://lore.kernel.org/linux-pci/20240418174043.3750240-1-vidyas@nvidia.com/ )
> posted by me.
>
> Vidya Sagar (4):
> PCI: Move PRESERVE_BOOT_CONFIG _DSM evaluation to
> pci_register_host_bridge()
> PCI: of: Add of_pci_preserve_config() for per-host bridge support
> PCI: Unify ACPI and DT 'preserve config' support
> PCI: Use preserve_config in place of pci_flags
>
> drivers/acpi/pci_root.c | 12 ------
> drivers/pci/controller/pci-host-common.c | 4 --
> drivers/pci/of.c | 54 +++++++++++++++++++-----
> drivers/pci/pci-acpi.c | 22 ++++++++++
> drivers/pci/pci.h | 12 ++++++
> drivers/pci/probe.c | 34 ++++++++++-----
> 6 files changed, 101 insertions(+), 37 deletions(-)
Applied to pci/enumeration for v6.11, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-06-03 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 17:41 [PATCH V7 0/4] PCI: Add support for preserving boot configuration Vidya Sagar
2024-05-08 17:41 ` [PATCH V7 1/4] PCI: Move PRESERVE_BOOT_CONFIG _DSM evaluation to pci_register_host_bridge() Vidya Sagar
2024-05-08 17:41 ` [PATCH V7 2/4] PCI: of: Add of_pci_preserve_config() for per-host bridge support Vidya Sagar
2024-05-08 17:41 ` [PATCH V7 3/4] PCI: Unify ACPI and DT 'preserve config' support Vidya Sagar
2024-05-08 17:41 ` [PATCH V7 4/4] PCI: Use preserve_config in place of pci_flags Vidya Sagar
2024-05-17 5:35 ` [PATCH V7 0/4] PCI: Add support for preserving boot configuration Vidya Sagar
2024-06-03 7:52 ` Vidya Sagar
2024-06-03 21:21 ` Bjorn Helgaas [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=20240603212146.GA697762@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kthota@nvidia.com \
--cc=kw@linux.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mmaddireddy@nvidia.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sagar.tv@gmail.com \
--cc=treding@nvidia.com \
--cc=vidyas@nvidia.com \
--cc=will@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