From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: will@kernel.org, lpieralisi@kernel.org, kw@linux.com,
robh@kernel.org, bhelgaas@google.com, krzk+dt@kernel.org,
conor+dt@kernel.org, liviu.dudau@arm.com, sudeep.holla@arm.com,
joro@8bytes.org
Cc: robin.murphy@arm.com, nicolinc@nvidia.com, ketanp@nvidia.com,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
iommu@lists.linux.dev, devicetree@vger.kernel.org,
Jean-Philippe Brucker <jean-philippe@linaro.org>
Subject: [PATCH 0/3] Enable PCIe ATS for devicetree boot
Date: Mon, 29 Apr 2024 12:39:36 +0100 [thread overview]
Message-ID: <20240429113938.192706-2-jean-philippe@linaro.org> (raw)
Before enabling Address Translation Support (ATS) in endpoints, the OS
needs to confirm that the Root Complex supports it. Obtain this
information from the firmware description since there is no architected
method. ACPI provides a bit via IORT tables, so add the devicetree
equivalent.
It was discussed a while ago [1], but at the time only a software model
supported it. Respin it now that hardware is available [2].
To test this with the Arm RevC model, enable ATS in the endpoint and
note that ATS is enabled. Address translation is transparent to the OS.
-C pci.pcie_rc.ahci0.endpoint.ats_supported=1
$ lspci -s 00:1f.0 -vv
Capabilities: [100 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
[1] https://lore.kernel.org/linux-iommu/20200213165049.508908-1-jean-philippe@linaro.org/
[2] https://lore.kernel.org/linux-arm-kernel/ZeJP6CwrZ2FSbTYm@Asurada-Nvidia/
Jean-Philippe Brucker (3):
dt-bindings: PCI: generic: Add ats-supported property
iommu/of: Support ats-supported device-tree property
arm64: dts: fvp: Enable PCIe ATS for Base RevC FVP
.../devicetree/bindings/pci/host-generic-pci.yaml | 6 ++++++
drivers/iommu/of_iommu.c | 9 +++++++++
arch/arm64/boot/dts/arm/fvp-base-revc.dts | 1 +
3 files changed, 16 insertions(+)
--
2.44.0
next reply other threads:[~2024-04-29 11:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 11:39 Jean-Philippe Brucker [this message]
2024-04-29 11:39 ` [PATCH 1/3] dt-bindings: PCI: generic: Add ats-supported property Jean-Philippe Brucker
2024-04-30 10:22 ` Liviu Dudau
2024-04-29 11:39 ` [PATCH 2/3] iommu/of: Support ats-supported device-tree property Jean-Philippe Brucker
2024-04-29 15:00 ` Jason Gunthorpe
2024-04-30 10:23 ` Liviu Dudau
2024-04-30 13:57 ` Robin Murphy
2024-05-02 4:55 ` Nicolin Chen
2024-04-29 11:39 ` [PATCH 3/3] arm64: dts: fvp: Enable PCIe ATS for Base RevC FVP Jean-Philippe Brucker
2024-05-16 10:44 ` Sudeep Holla
2024-05-15 18:28 ` [PATCH 0/3] Enable PCIe ATS for devicetree boot Vidya Sagar
2024-05-15 18:52 ` Bjorn Helgaas
2024-05-16 7:35 ` Jean-Philippe Brucker
2024-05-16 10:41 ` Sudeep Holla
2024-05-16 11:42 ` Jean-Philippe Brucker
2024-05-21 10:25 ` liviu.dudau
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=20240429113938.192706-2-jean-philippe@linaro.org \
--to=jean-philippe@linaro.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=ketanp@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sudeep.holla@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).