Re: [PATCH 1/8] dt-bindings: dma: nvidia,tegra186-gpc-dma: Add iommu-map property

[Akhil R <akhilrajeev@nvidia.com>]

On Wed, 18 Feb 2026 09:49:28 -0600, Rob Herring wrote:
> On Wed, Feb 18, 2026 at 3:59 AM Jon Hunter <jonathanh@nvidia.com> wrote:
>>
>>
>> On 17/02/2026 19:53, Krzysztof Kozlowski wrote:
>>> On 17/02/2026 18:34, Akhil R wrote:
>>>> Add iommu-map property which helps when each channel requires its own
>>>> stream ID for the transfer. Use iommu-map to specify separate stream
>>>> ID for each channel. This enables each channel to be in its own iommu
>>>> domain and keeps the memory isolated from other devices sharing the
>>>> same DMA controller.
>>>>
>>>> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
>>>> ---
>>>>   .../devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml  | 8 ++++++++
>>>>   1 file changed, 8 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml b/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
>>>> index 0dabe9bbb219..542e9cb9f641 100644
>>>> --- a/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
>>>> +++ b/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
>>>> @@ -14,6 +14,7 @@ description: |
>>>>   maintainers:
>>>>     - Jon Hunter <jonathanh@nvidia.com>
>>>>     - Rajesh Gumasta <rgumasta@nvidia.com>
>>>> +  - Akhil R <akhilrajeev@nvidia.com>
>>>
>>> With 4.5 trillion USD capitalization of Nvidia one could assume they can
>>> spare few resources to test the patch before sending it... instead of
>>> relying on Rob's and my machines to do that for them.
>>>
>>> Expect grumpy review because you do not care about our time.
>>
>>
>> ACK! We need to do a better job here. I will work with Akhil to improve
>> this.
>
> Anyone that wants to run a gitlab-runner (and docker) on one of their
> machines to add to the test capacity would be more than welcomed. It's
> pretty trivial to set up. The only requirement is something faster
> than gitlab shared runners. My 2 machines are M1 and M3 MBPs.

I did not realise that the system I used had a very old version of dtschema
where these errors did not show up. I do see them now once I upgraded the
dtschema. Will fix these and test them in the next revision. 

Regards,
Akhil