Linux SPI subsystem development
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Conor Dooley <conor@kernel.org>, Vishwaroop A <va@nvidia.com>
Cc: krzk@kernel.org, broonie@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	thierry.reding@gmail.com, skomatineni@nvidia.com,
	ldewangan@nvidia.com, kyarlagadda@nvidia.com,
	smangipudi@nvidia.com, bgriffis@nvidia.com,
	linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 RESEND 1/2] dt-bindings: spi: tegra: Document IOMMU property for Tegra234 QSPI
Date: Tue, 13 May 2025 11:19:05 +0100	[thread overview]
Message-ID: <904d3e89-a540-4edd-b748-15e13c431c17@nvidia.com> (raw)
In-Reply-To: <20250512-observant-rental-21927c85c709@spud>


On 12/05/2025 17:49, Conor Dooley wrote:
> On Fri, May 09, 2025 at 04:54:08PM +0000, Vishwaroop A wrote:
>> Add the 'iommus' property to the Tegra QSPI device tree binding.
>> The property is needed for Tegra234 when using the internal DMA
>> controller, and is not supported on other Tegra chips, as DMA is
>> handled by an external controller.
>>
>> Signed-off-by: Vishwaroop A <va@nvidia.com>
>> ---
>>   .../bindings/spi/nvidia,tegra210-quad.yaml    | 19 ++++++++++++++++---
>>   1 file changed, 16 insertions(+), 3 deletions(-)
>>
>> Changes since v2:
>> - Fixed version number to match the actual version
>> - Added proper changelog section
>> - No functional changes from v2
>>
>> Changes since v1:
>> - Fixed subject prefix to match subsystem (dt-bindings: spi: tegra)
>> - Improved commit message formatting to follow Linux coding style
>> - Clarified that IOMMU is only required for Tegra234 platform
>> - Added explicit disallow for IOMMU on other platforms
>> - Removed redundant explanations of what the patch does
>> - Fixed commit message to use imperative mood
>>
>> Initial Version:
>> - Initial implementation of IOMMU property documentation
>> - Added iommus property to device tree binding
>> - Added support for Tegra234 platform
>> - Added explanation of DMA and IOMMU requirements
>>
>> diff --git a/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml b/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml
>> index 48e97e240265..04d3b1a47392 100644
>> --- a/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml
>> +++ b/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml
>> @@ -10,9 +10,6 @@ maintainers:
>>     - Thierry Reding <thierry.reding@gmail.com>
>>     - Jonathan Hunter <jonathanh@nvidia.com>
>>   
>> -allOf:
>> -  - $ref: spi-controller.yaml#
>> -
>>   properties:
>>     compatible:
>>       enum:
>> @@ -47,6 +44,9 @@ properties:
>>         - const: rx
>>         - const: tx
>>   
>> +  iommus:
>> +    maxItems: 1
>> +
>>   patternProperties:
>>     "@[0-9a-f]+$":
>>       type: object
>> @@ -69,6 +69,19 @@ required:
>>   
>>   unevaluatedProperties: false
>>   
>> +allOf:
>> +  - $ref: spi-controller.yaml#
>> +  - if:
>> +      properties:
>> +        compatible:
>> +          const: nvidia,tegra234-qspi
> 
>> +    then:
>> +      properties:
>> +        iommus: true
> 
> This is a NOP, no?
> Just invert the case above and drop a clause.


Yes that's true. So just to confirm, your preference is this ...

diff --git 
a/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml 
b/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml
index 04d3b1a47392..c45511e9a9ed 100644
--- a/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml
+++ b/Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml
@@ -74,11 +74,13 @@ allOf:
    - if:
        properties:
          compatible:
-          const: nvidia,tegra234-qspi
+          contains:
+            enum:
+              - nvidia,tegra210-qspi
+              - nvidia,tegra186-qspi
+              - nvidia,tegra194-qspi
+              - nvidia,tegra241-qspi
      then:
-      properties:
-        iommus: true
-    else:
        properties:
          iommus: false

Thanks!
Jon

-- 
nvpublic


  reply	other threads:[~2025-05-13 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 16:54 [PATCH V3 RESEND 1/2] dt-bindings: spi: tegra: Document IOMMU property for Tegra234 QSPI Vishwaroop A
2025-05-09 16:54 ` [PATCH V3 RESEND 2/2] spi: tegra210-quad: Add support for internal DMA Vishwaroop A
2025-05-12 16:49 ` [PATCH V3 RESEND 1/2] dt-bindings: spi: tegra: Document IOMMU property for Tegra234 QSPI Conor Dooley
2025-05-13 10:19   ` Jon Hunter [this message]
2025-05-13 10:59     ` Conor Dooley

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=904d3e89-a540-4edd-b748-15e13c431c17@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=bgriffis@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kyarlagadda@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=skomatineni@nvidia.com \
    --cc=smangipudi@nvidia.com \
    --cc=thierry.reding@gmail.com \
    --cc=va@nvidia.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