From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: memory: tegra: Add Tegra264 support
Date: Wed, 9 Jul 2025 20:19:51 +0200 [thread overview]
Message-ID: <abbfc54d-96af-4e9d-8c2c-8965aa99076b@kernel.org> (raw)
In-Reply-To: <20250708105245.1516143-2-thierry.reding@gmail.com>
On 08/07/2025 12:52, Thierry Reding wrote:
> interrupts:
> - items:
> - - description: MC general interrupt
> + minItems: 1
> + maxItems: 8
> +
> + interrupt-names:
> + minItems: 1
> + maxItems: 8
>
> "#address-cells":
> const: 2
> @@ -74,6 +79,7 @@ patternProperties:
> - nvidia,tegra186-emc
> - nvidia,tegra194-emc
> - nvidia,tegra234-emc
> + - nvidia,tegra264-emc
>
> reg:
> minItems: 1
> @@ -127,6 +133,15 @@ patternProperties:
> reg:
> minItems: 2
>
> + - if:
> + properties:
> + compatible:
> + const: nvidia,tegra264-emc
> + then:
> + properties:
> + reg:
> + minItems: 2
> +
> additionalProperties: false
>
> required:
> @@ -220,6 +235,52 @@ allOf:
> - const: ch14
> - const: ch15
>
> + - if:
> + properties:
> + compatible:
> + const: nvidia,tegra264-mc
> + then:
> + properties:
> + reg:
> + minItems: 17
Missing maxItems
> + description: 17 memory controller channels
> +
> + reg-names:
> + items:
> + - const: broadcast
> + - const: ch0
> + - const: ch1
> + - const: ch2
> + - const: ch3
> + - const: ch4
> + - const: ch5
> + - const: ch6
> + - const: ch7
> + - const: ch8
> + - const: ch9
> + - const: ch10
> + - const: ch11
> + - const: ch12
> + - const: ch13
> + - const: ch14
> + - const: ch15
> +
> + interrupts:
> + minItems: 8
> + maxItems: 8
> + description: One interrupt line for each MC component
> +
> + interrupt-names:
> + items:
> + - const: mcf
> + - const: hub1
> + - const: hub2
> + - const: hub3
> + - const: hub4
> + - const: hub5
> + - const: sbs
> + - const: channel
Missing constraints for interrupts and interrupt-names for all other
variants. Now this patch claims they all have 8 interrupts with any name.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-09 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 10:52 [PATCH 0/4] " Thierry Reding
2025-07-08 10:52 ` [PATCH 1/4] dt-bindings: " Thierry Reding
2025-07-09 18:19 ` Krzysztof Kozlowski [this message]
2025-07-09 20:36 ` Thierry Reding
2025-07-10 6:42 ` Krzysztof Kozlowski
2025-07-08 10:52 ` [PATCH 2/4] dt-bindings: memory: tegra: Add Tegra264 definitions Thierry Reding
2025-07-09 18:20 ` Krzysztof Kozlowski
2025-07-09 20:37 ` Thierry Reding
2025-07-08 10:52 ` [PATCH 3/4] dt-bindings: memory: tegra: Add Tegra264 stream IDs Thierry Reding
2025-07-09 18:21 ` Krzysztof Kozlowski
2025-07-09 20:39 ` Thierry Reding
2025-07-08 10:52 ` [PATCH 4/4] memory: tegra: Add Tegra264 MC and EMC support Thierry Reding
2025-07-09 18:23 ` Krzysztof Kozlowski
2025-07-09 12:18 ` [PATCH 0/4] memory: tegra: Add Tegra264 support Thierry Reding
2025-07-09 18:18 ` Krzysztof Kozlowski
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=abbfc54d-96af-4e9d-8c2c-8965aa99076b@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®