The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mikko Perttunen <mperttunen@nvidia.com>
To: devicetree@vger.kernel.org
Cc: "Bartosz Golaszewski" <brgl@kernel.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Thierry Reding" <thierry.reding@kernel.org>,
	"Jonathan Hunter" <jonathanh@nvidia.com>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
	"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH 1/6] dt-bindings: PCI: tegra264: Allow the ats-supported property
Date: Fri, 20 Nov 2026 10:12:11 +0900	[thread overview]
Message-ID: <meFC-rbZSSu9SGIB4wyt6A@nvidia.com> (raw)
In-Reply-To: <20261119201817.GA119016-robh@kernel.org>

On Friday, November 20, 2026 5:18 AM Rob Herring wrote:
> On Thu, Oct 29, 2026 at 12:32:03PM +0900, Mikko Perttunen wrote:
> > The C0 controller on Tegra264 is connected to the integrated GPU, which
> > issues ATS requests. Add the ats-supported property to allow marking
> > ATS as supported on the controller.
> > 
> > Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
> > ---
> >  Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml | 5 +++++
> >  1 file changed, 5 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml b/Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml
> > index f0114defc04e..3b4f31a4a4c2 100644
> > --- a/Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml
> > +++ b/Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml
> > @@ -34,6 +34,11 @@ properties:
> >  
> >    dma-coherent: true
> >  
> > +  ats-supported:
> > +    description:
> > +      Indicates that the controller supports ATS.
> > +    type: boolean
> 
> 2 users of this now. This needs to be moved into pci-host-bridge.yaml.

I have opened a pull request:

	https://github.com/devicetree-org/dt-schema/pull/215

Any other changes required on the kernel side?

If we need to wait for a dt-schema release cycle before the definition 
is considered available, can we merge this patch for now and revert 
later along with the definition in host-generic-pci? In any case, I can 
send a patch to remove the host-generic-pci definition later.

Thanks
Mikko

> 
> > +
> >    nvidia,bpmp:
> >      $ref: /schemas/types.yaml#/definitions/phandle-array
> >      description: |
> > 
> > -- 
> > 2.55.0
> > 
> 





  reply	other threads:[~2026-11-20  1:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  3:32 [PATCH 0/6] Tegra264 GB10B boards the bus Mikko Perttunen
2026-10-29  3:32 ` [PATCH 1/6] dt-bindings: PCI: tegra264: Allow the ats-supported property Mikko Perttunen
2026-11-19 20:18   ` Rob Herring
2026-11-20  1:12     ` Mikko Perttunen [this message]
2026-10-29  3:32 ` [PATCH 2/6] PCI/pwrctrl: Enable pwrctrl for devices powered by a power domain Mikko Perttunen
2026-10-30 11:42   ` Bartosz Golaszewski
2026-10-29  3:32 ` [PATCH 3/6] PCI/pwrctrl: Add the Tegra264 iGPU to the generic match table Mikko Perttunen
2026-10-30 11:43   ` Bartosz Golaszewski
2026-10-29  3:32 ` [PATCH 4/6] PCI: tegra264: Power endpoint devices before enumeration Mikko Perttunen
2026-10-30 11:44   ` Bartosz Golaszewski
2026-10-29  3:32 ` [PATCH 5/6] arm64: tegra: Add node for the GB10B GPU on Tegra264 Mikko Perttunen
2026-11-17 12:17   ` Thierry Reding
2026-11-18  0:30     ` Mikko Perttunen
2026-11-18 12:49       ` Thierry Reding
2026-10-29  3:32 ` [PATCH 6/6] arm64: tegra: Enable and mark the Tegra264 GPU PCIe controller as ATS supported Mikko Perttunen

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=meFC-rbZSSu9SGIB4wyt6A@nvidia.com \
    --to=mperttunen@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@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