public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: "Krzysztof Wilczyński" <kw@linux.com>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
	lpieralisi@kernel.org, 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, 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
Subject: Re: [PATCH v2 1/3] dt-bindings: PCI: generic: Add ats-supported property
Date: Mon, 8 Jul 2024 10:36:31 +0100	[thread overview]
Message-ID: <20240708093630.GA11302@willie-the-truck> (raw)
In-Reply-To: <20240706032431.GH1195499@rocinante>

Hi Krzysztof,

On Sat, Jul 06, 2024 at 12:24:31PM +0900, Krzysztof Wilczyński wrote:
> > Add a way for firmware to tell the OS that ATS is supported by the PCI
> > root complex. An endpoint with ATS enabled may send Translation Requests
> > and Translated Memory Requests, which look just like Normal Memory
> > Requests with a non-zero AT field. So a root controller that ignores the
> > AT field may simply forward the request to the IOMMU as a Normal Memory
> > Request, which could end badly. In any case, the endpoint will be
> > unusable.
> > 
> > The ats-supported property allows the OS to only enable ATS in endpoints
> > if the root controller can handle ATS requests. Only add the property to
> > pcie-host-ecam-generic for the moment. For non-generic root controllers,
> > availability of ATS can be inferred from the compatible string.
> 
> Applied to dt-bindings, thank you!
> 
> [1/1] dt-bindings: PCI: generic: Add ats-supported property
>       https://git.kernel.org/pci/pci/c/631b2e7318d45

FWIW: I already picked this up in the IOMMU tree last week. If you need
it to avoid a conflict, then you can pull from the pci/ats branch:

https://git.kernel.org/pub/scm/linux/kernel/git/iommu/linux.git/commit/?h=pci/ats&id=40929e8e5449a18bc98baf7a907dd6674bd60049

Cheers,

Will


  reply	other threads:[~2024-07-08  9:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 10:54 [PATCH v2 0/3] Enable PCIe ATS for devicetree boot Jean-Philippe Brucker
2024-06-07 10:54 ` [PATCH v2 1/3] dt-bindings: PCI: generic: Add ats-supported property Jean-Philippe Brucker
2024-07-06  3:24   ` Krzysztof Wilczyński
2024-07-08  9:36     ` Will Deacon [this message]
2024-06-07 10:54 ` [PATCH v2 2/3] iommu/of: Support ats-supported device-tree property Jean-Philippe Brucker
2024-06-07 10:54 ` [PATCH v2 3/3] arm64: dts: fvp: Enable PCIe ATS for Base RevC FVP Jean-Philippe Brucker
2024-07-01 10:24 ` [PATCH v2 0/3] Enable PCIe ATS for devicetree boot Jean-Philippe Brucker
2024-07-01 11:57   ` Will Deacon
2024-07-01 13:02     ` Jean-Philippe Brucker
2024-07-04 14:18 ` Will Deacon

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=20240708093630.GA11302@willie-the-truck \
    --to=will@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --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 \
    /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