From: Ashish Mhetre <amhetre@nvidia.com>
To: Jon Hunter <jonathanh@nvidia.com>,
will@kernel.org, robin.murphy@arm.com, joro@8bytes.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
nicolinc@nvidia.com
Cc: thierry.reding@gmail.com, vdumpa@nvidia.com, jgg@ziepe.ca,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2 3/3] arm64: dts: nvidia: Add nodes for CMDQV
Date: Mon, 1 Dec 2025 15:06:55 +0530 [thread overview]
Message-ID: <acae92d8-3394-436c-be8e-8bed7a923e85@nvidia.com> (raw)
In-Reply-To: <dff3a962-82dd-4aac-ae11-69f0e95ba04d@nvidia.com>
On 11/25/2025 3:52 PM, Jon Hunter wrote:
>
>
> On 25/11/2025 07:16, Ashish Mhetre wrote:
>> The Command Queue Virtualization (CMDQV) hardware is part of the
>> SMMUv3 implementation on NVIDIA Tegra SoCs. It assists in
>> virtualizing the command queue for the SMMU.
>>
>> Update SMMU compatible strings to use nvidia,tegra264-smmu to enable
>> CMDQV support. Add device tree nodes for the CMDQV hardware and enable
>> them on the tegra264-p3834 platform where SMMUs are enabled. Each SMMU
>> instance is paired with its corresponding CMDQV instance via the
>> nvidia,cmdqv property.
>>
>> Signed-off-by: Ashish Mhetre <amhetre@nvidia.com>
>> ---
>> .../arm64/boot/dts/nvidia/tegra264-p3834.dtsi | 8 +++
>> arch/arm64/boot/dts/nvidia/tegra264.dtsi | 55 +++++++++++++++++--
>> 2 files changed, 58 insertions(+), 5 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi
>> b/arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi
>> index 06795c82427a..375d122b92fa 100644
>> --- a/arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi
>> +++ b/arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi
>> @@ -26,5 +26,13 @@ iommu@5000000 {
>> iommu@6000000 {
>> status = "okay";
>> };
>> +
>> + cmdqv@5200000 {
>> + status = "okay";
>> + };
>
> This needs to be ordered in the file according to its address.
Hi Jon, Thanks for the review.
cmdqv nodes follow same ordering as its corresponding iommu nodes.
I have added them immediately after corresponding iommu nodes.
Can you please check and see if it's fine? Same applies to your
similar comments below as well.
>
>> +
>> + cmdqv@6200000 {
>> + status = "okay";
>> + };
>> };
>> };
>> diff --git a/arch/arm64/boot/dts/nvidia/tegra264.dtsi
>> b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
>> index f137565da804..d8287b95221e 100644
>> --- a/arch/arm64/boot/dts/nvidia/tegra264.dtsi
>> +++ b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
>> @@ -3361,7 +3361,7 @@ bus@8100000000 {
>> <0x02 0x00000000 0xd0 0x00000000 0x08 0x80000000>; /*
>> ECAM, prefetchable memory, I/O */
>> smmu1: iommu@5000000 {
>> - compatible = "arm,smmu-v3";
>> + compatible = "nvidia,tegra264-smmu", "arm,smmu-v3";
>> reg = <0x00 0x5000000 0x0 0x200000>;
>> interrupts = <GIC_SPI 12 IRQ_TYPE_EDGE_RISING>,
>> <GIC_SPI 13 IRQ_TYPE_EDGE_RISING>;
>> @@ -3370,10 +3370,11 @@ smmu1: iommu@5000000 {
>> #iommu-cells = <1>;
>> dma-coherent;
>> + nvidia,cmdqv = <&cmdqv1>;
>> };
>> smmu2: iommu@6000000 {
>> - compatible = "arm,smmu-v3";
>> + compatible = "nvidia,tegra264-smmu", "arm,smmu-v3";
>> reg = <0x00 0x6000000 0x0 0x200000>;
>> interrupts = <GIC_SPI 1 IRQ_TYPE_EDGE_RISING>,
>> <GIC_SPI 2 IRQ_TYPE_EDGE_RISING>;
>> @@ -3382,6 +3383,23 @@ smmu2: iommu@6000000 {
>> #iommu-cells = <1>;
>> dma-coherent;
>> + nvidia,cmdqv = <&cmdqv2>;
>> + };
>> +
>> + cmdqv1: cmdqv@5200000 {
>
> Same here. Please order according to the address.
>
>> + compatible = "nvidia,tegra264-cmdqv";
>> + status = "disabled";
>> +
>> + reg = <0x00 0x5200000 0x0 0x830000>;
>> + interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>;
>> + };
>> +
>> + cmdqv2: cmdqv@6200000 {
>> + compatible = "nvidia,tegra264-cmdqv";
>> + status = "disabled";
>> +
>> + reg = <0x00 0x6200000 0x0 0x830000>;
>> + interrupts = <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>;
>> };
>> mc: memory-controller@8020000 {
>> @@ -3437,7 +3455,7 @@ emc: external-memory-controller@8800000 {
>> };
>> smmu0: iommu@a000000 {
>> - compatible = "arm,smmu-v3";
>> + compatible = "nvidia,tegra264-smmu", "arm,smmu-v3";
>> reg = <0x00 0xa000000 0x0 0x200000>;
>> interrupts = <GIC_SPI 21 IRQ_TYPE_EDGE_RISING>,
>> <GIC_SPI 22 IRQ_TYPE_EDGE_RISING>;
>> @@ -3446,10 +3464,11 @@ smmu0: iommu@a000000 {
>> #iommu-cells = <1>;
>> dma-coherent;
>> + nvidia,cmdqv = <&cmdqv0>;
>> };
>> smmu4: iommu@b000000 {
>> - compatible = "arm,smmu-v3";
>> + compatible = "nvidia,tegra264-smmu", "arm,smmu-v3";
>> reg = <0x00 0xb000000 0x0 0x200000>;
>> interrupts = <GIC_SPI 30 IRQ_TYPE_EDGE_RISING>,
>> <GIC_SPI 31 IRQ_TYPE_EDGE_RISING>;
>> @@ -3458,6 +3477,23 @@ smmu4: iommu@b000000 {
>> #iommu-cells = <1>;
>> dma-coherent;
>> + nvidia,cmdqv = <&cmdqv4>;
>> + };
>> +
>> + cmdqv0: cmdqv@a200000 {
>
> And here.
>
>> + compatible = "nvidia,tegra264-cmdqv";
>> + status = "disabled";
>> +
>> + reg = <0x00 0xa200000 0x0 0x830000>;
>> + interrupts = <GIC_SPI 28 IRQ_TYPE_LEVEL_HIGH>;
>> + };
>> +
>> + cmdqv4: cmdqv@b200000 {
>> + compatible = "nvidia,tegra264-cmdqv";
>> + status = "disabled";
>> +
>> + reg = <0x00 0xb200000 0x0 0x830000>;
>> + interrupts = <GIC_SPI 37 IRQ_TYPE_LEVEL_HIGH>;
>> };
>> i2c14: i2c@c410000 {
>> @@ -3690,7 +3726,7 @@ bus@8800000000 {
>> ranges = <0x00 0x00000000 0x88 0x00000000 0x01 0x00000000>;
>> smmu3: iommu@6000000 {
>> - compatible = "arm,smmu-v3";
>> + compatible = "nvidia,tegra264-smmu", "arm,smmu-v3";
>> reg = <0x00 0x6000000 0x0 0x200000>;
>> interrupts = <GIC_SPI 225 IRQ_TYPE_EDGE_RISING>,
>> <GIC_SPI 226 IRQ_TYPE_EDGE_RISING>;
>> @@ -3699,6 +3735,15 @@ smmu3: iommu@6000000 {
>> #iommu-cells = <1>;
>> dma-coherent;
>> + nvidia,cmdqv = <&cmdqv3>;
>> + };
>> +
>> + cmdqv3: cmdqv@6200000 {
>> + compatible = "nvidia,tegra264-cmdqv";
>> + status = "disabled";
>> +
>> + reg = <0x00 0x6200000 0x0 0x830000>;
>> + interrupts = <GIC_SPI 232 IRQ_TYPE_LEVEL_HIGH>;
>> };
>> hda@90b0000 {
>
next prev parent reply other threads:[~2025-12-01 9:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 7:16 [PATCH V2 0/3] Add device tree support for NVIDIA Tegra CMDQV Ashish Mhetre
2025-11-25 7:16 ` [PATCH V2 1/3] iommu/arm-smmu-v3: Add device-tree support for CMDQV driver Ashish Mhetre
2025-11-25 17:25 ` Robin Murphy
2025-12-01 15:55 ` Ashish Mhetre
2025-11-25 7:16 ` [PATCH V2 2/3] dt-bindings: iommu: Add NVIDIA Tegra CMDQV support Ashish Mhetre
2025-11-25 7:16 ` [PATCH V2 3/3] arm64: dts: nvidia: Add nodes for CMDQV Ashish Mhetre
2025-11-25 10:22 ` Jon Hunter
2025-12-01 9:36 ` Ashish Mhetre [this message]
2025-12-01 14:11 ` Thierry Reding
2025-12-01 15:54 ` Ashish Mhetre
2025-12-01 14:13 ` Robin Murphy
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=acae92d8-3394-436c-be8e-8bed7a923e85@nvidia.com \
--to=amhetre@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=thierry.reding@gmail.com \
--cc=vdumpa@nvidia.com \
--cc=will@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