From: Thierry Reding <thierry.reding@gmail.com>
To: Rayyan Ansari <rayyan@ansari.sh>
Cc: linux-tegra@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: tegra: Enable IOMMU for host1x on Tegra132
Date: Wed, 16 Aug 2023 18:24:01 +0200 [thread overview]
Message-ID: <ZNz4IZ8lSXlGIZb_@orome> (raw)
In-Reply-To: <20230810214543.16235-1-rayyan@ansari.sh>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
On Thu, Aug 10, 2023 at 10:45:41PM +0100, Rayyan Ansari wrote:
> Add the iommu property to the host1x node to register it with its
> swgroup.
>
> Signed-off-by: Rayyan Ansari <rayyan@ansari.sh>
> ---
> arch/arm64/boot/dts/nvidia/tegra132.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
Do you happen to have a Tegra132 device that you can test upstream Linux
on? Just asking out of curiosity because these devices are becoming very
rare these days and it'd be good to know if people are still using these
and that recent Linux kernels are still running on them.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-16 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 21:45 [PATCH] arm64: tegra: Enable IOMMU for host1x on Tegra132 Rayyan Ansari
2023-08-16 16:24 ` Thierry Reding [this message]
2023-08-16 19:56 ` Rayyan Ansari
2023-08-16 20:09 ` Rayyan Ansari
2023-08-16 16:24 ` Thierry Reding
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=ZNz4IZ8lSXlGIZb_@orome \
--to=thierry.reding@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rayyan@ansari.sh \
--cc=robh+dt@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 NNTP newsgroup(s).