From: sashiko-bot@kernel.org
To: "Mikko Perttunen" <mperttunen@nvidia.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH 6/6] arm64: tegra: Enable and mark the Tegra264 GPU PCIe controller as ATS supported
Date: Thu, 29 Oct 2026 03:42:05 +0000 [thread overview]
Message-ID: <sashiko-outbox-188677@kernel.org> (raw)
In-Reply-To: <20261029-b4-t264-igpu-pci-v1-6-4d843dda0b02@nvidia.com>
> PCIe C0 connects to the integrated GPU and is internal to the SoC.
> Therefore enable it directly in the SoC device tree file.
>
> At the same time, mark it as ats-supported -- the GPU issues ATS
> requests and this is required to enable their handling.
>
> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261029-b4-t264-igpu-pci-v1-0-4d843dda0b02@nvidia.com?part=6
prev parent reply other threads:[~2026-10-29 3:42 UTC|newest]
Thread overview: 13+ 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-10-29 3:38 ` sashiko-bot
2026-10-29 3:32 ` [PATCH 2/6] PCI/pwrctrl: Enable pwrctrl for devices powered by a power domain Mikko Perttunen
2026-10-29 3:42 ` sashiko-bot
2026-10-29 3:32 ` [PATCH 3/6] PCI/pwrctrl: Add the Tegra264 iGPU to the generic match table Mikko Perttunen
2026-10-29 3:41 ` sashiko-bot
2026-10-29 3:32 ` [PATCH 4/6] PCI: tegra264: Power endpoint devices before enumeration Mikko Perttunen
2026-10-29 3:42 ` sashiko-bot
2026-10-29 3:32 ` [PATCH 5/6] arm64: tegra: Add node for the GB10B GPU on Tegra264 Mikko Perttunen
2026-10-29 3:41 ` sashiko-bot
2026-10-29 3:32 ` [PATCH 6/6] arm64: tegra: Enable and mark the Tegra264 GPU PCIe controller as ATS supported Mikko Perttunen
2026-10-29 3:42 ` sashiko-bot [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=sashiko-outbox-188677@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=sashiko-reviews@lists.linux.dev \
/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