From: Bjorn Helgaas <helgaas@kernel.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-pci <linux-pci@vger.kernel.org>,
Sinan Kaya <okaya@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [RFC PATCH v2] arm64: acpi/pci: invoke _DSM whether to preserve firmware PCI setup
Date: Fri, 14 Jun 2019 08:12:53 -0500 [thread overview]
Message-ID: <20190614131253.GR13533@google.com> (raw)
In-Reply-To: <84320a45ef9395d82bf1c5d4d2d7e6db189cbfda.camel@kernel.crashing.org>
On Fri, Jun 14, 2019 at 08:43:19PM +1000, Benjamin Herrenschmidt wrote:
> This least to another conversation we hinted at earlier.. we should
> probably have a way to do the same at least for BARs on ACPI systems so
> we don't have to temporarily disable access to a device to size them.
The PCI Enhanced Allocation capability provides a way to do this. I
don't know how widely used it is, but it's theoretically possible.
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-pci <linux-pci@vger.kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Sinan Kaya <okaya@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [RFC PATCH v2] arm64: acpi/pci: invoke _DSM whether to preserve firmware PCI setup
Date: Fri, 14 Jun 2019 08:12:53 -0500 [thread overview]
Message-ID: <20190614131253.GR13533@google.com> (raw)
In-Reply-To: <84320a45ef9395d82bf1c5d4d2d7e6db189cbfda.camel@kernel.crashing.org>
On Fri, Jun 14, 2019 at 08:43:19PM +1000, Benjamin Herrenschmidt wrote:
> This least to another conversation we hinted at earlier.. we should
> probably have a way to do the same at least for BARs on ACPI systems so
> we don't have to temporarily disable access to a device to size them.
The PCI Enhanced Allocation capability provides a way to do this. I
don't know how widely used it is, but it's theoretically possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-14 13:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 7:54 [RFC PATCH v2] arm64: acpi/pci: invoke _DSM whether to preserve firmware PCI setup Benjamin Herrenschmidt
2019-06-13 7:54 ` Benjamin Herrenschmidt
2019-06-13 19:02 ` Bjorn Helgaas
2019-06-13 19:02 ` Bjorn Helgaas
2019-06-13 21:59 ` Benjamin Herrenschmidt
2019-06-13 21:59 ` Benjamin Herrenschmidt
2019-06-13 23:07 ` Benjamin Herrenschmidt
2019-06-13 23:07 ` Benjamin Herrenschmidt
2019-06-14 7:42 ` Ard Biesheuvel
2019-06-14 7:42 ` Ard Biesheuvel
2019-06-14 8:36 ` Benjamin Herrenschmidt
2019-06-14 8:36 ` Benjamin Herrenschmidt
2019-06-14 9:57 ` Lorenzo Pieralisi
2019-06-14 9:57 ` Lorenzo Pieralisi
2019-06-14 10:36 ` Benjamin Herrenschmidt
2019-06-14 10:36 ` Benjamin Herrenschmidt
2019-06-14 10:43 ` Benjamin Herrenschmidt
2019-06-14 10:43 ` Benjamin Herrenschmidt
2019-06-14 13:12 ` Bjorn Helgaas [this message]
2019-06-14 13:12 ` Bjorn Helgaas
2019-06-14 13:48 ` Benjamin Herrenschmidt
2019-06-14 13:48 ` Benjamin Herrenschmidt
2019-06-14 20:13 ` Bjorn Helgaas
2019-06-14 20:13 ` Bjorn Helgaas
2019-06-15 1:18 ` Benjamin Herrenschmidt
2019-06-15 1:18 ` Benjamin Herrenschmidt
2019-06-14 13:09 ` Bjorn Helgaas
2019-06-14 13:09 ` Bjorn Helgaas
2019-06-14 13:46 ` Benjamin Herrenschmidt
2019-06-14 13:46 ` Benjamin Herrenschmidt
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=20190614131253.GR13533@google.com \
--to=helgaas@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=okaya@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 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.