From: Rayyan Ansari <rayyan@ansari.sh>
To: Thierry Reding <thierry.reding@gmail.com>
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 21:09:49 +0100 [thread overview]
Message-ID: <fa2f0e13-1576-7985-5702-80cba3ecb17f@ansari.sh> (raw)
In-Reply-To: <b07819ea-4a96-0906-b8e9-a9b045c37032@ansari.sh>
On 16/08/2023 20:56, Rayyan Ansari wrote:
> On 16/08/2023 17:24, Thierry Reding wrote:
>> 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.
>
> I do - I have the Nexus 9. At some point I was trying to mainline it,
> but I stopped as I couldn't manage to get USB working - I only got
> simplefb working. If it would be useful I could see if my old patches
> work now and submit them.
I looked through my old notes and I was able to get USB host mode (ie
USB OTG) working but not USB device mode.
>
>>
>> Thierry
>
--
Rayyan Ansari
https://ansari.sh
next prev parent reply other threads:[~2023-08-16 20:11 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
2023-08-16 19:56 ` Rayyan Ansari
2023-08-16 20:09 ` Rayyan Ansari [this message]
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=fa2f0e13-1576-7985-5702-80cba3ecb17f@ansari.sh \
--to=rayyan@ansari.sh \
--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=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).