Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Patrick Fischer" <admin@tsv-stahl-riesa.de>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 4/6] dt-bindings: memory: tegra: Add Tegra114 EMC channel registers
Date: Wed, 11 Nov 2026 10:24:51 +0000	[thread overview]
Message-ID: <sashiko-outbox-208800@kernel.org> (raw)
In-Reply-To: <20261111-upstream-emc-t114-v1-4-54d9e1bceb6a@tsv-stahl-riesa.de>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] dt-bindings: memory: tegra: piling Tegra114 conditionals in
  tegra124-emc.yaml
--

commit d5391965f848eab5127dd4add5fff242e933a0a0
Author: Patrick Fischer <admin@tsv-stahl-riesa.de>

dt-bindings: memory: tegra: Add Tegra114 EMC channel registers

This commit updates the Tegra124 EMC binding schema to allow two optional
channel register blocks in the reg property for Tegra114 while restricting
Tegra124 to a single reg entry.

> diff --git a/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-emc.yaml b/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-emc.yaml
> index 8e0c67d671f91..c9335483ba850 100644
> --- a/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-emc.yaml
> +++ b/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-emc.yaml
> @@ -25,7 +25,13 @@ properties:
>            - const: nvidia,tegra124-emc
>  
>    reg:
> -    maxItems: 1
> +    oneOf:
> +      - items:
> +          - description: EMC registers, writes go to all channels
> +      - items:
> +          - description: EMC registers, writes go to all channels
> +          - description: EMC channel 0 registers
> +          - description: EMC channel 1 registers
>  
>    clocks:
>      items:
> @@ -218,6 +224,9 @@ allOf:
>              enum:
>                - nvidia,tegra124-emc
>      then:
> +      properties:
> +        reg:
> +          maxItems: 1
>        patternProperties:
>          "^emc-timings-[0-9]+$":
>            patternProperties:

[Severity: Low]
This isn't a bug, but would it be cleaner to split nvidia,tegra114-emc into
its own schema file rather than adding more per-compatible conditionals to
nvidia,tegra124-emc.yaml?

nvidia,tegra124-emc.yaml already relaxes nvidia,emc-configuration to a 97 to
143 entry range and uses an if-then block under allOf to require
nvidia,emc-bgbias-ctl0 and nvidia,emc-cfg-2 only on Tegra124. Widening the
top-level reg property and constraining it back in the conditional further
diverges the two variants, whereas Tegra20, Tegra30, and Tegra210 each use a
separate EMC binding schema.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261111-upstream-emc-t114-v1-0-54d9e1bceb6a@tsv-stahl-riesa.de?part=4

  reply	other threads:[~2026-11-11 10:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 10:10 [PATCH 0/6] memory: tegra114-emc: Fix bus width and pad auto-calibration Patrick Fischer via B4 Relay
2026-11-11 10:10 ` [PATCH 1/6] memory: tegra114-emc: Stop clearing EMC_AUTO_CAL_CONFIG Patrick Fischer via B4 Relay
2026-11-11 10:10 ` [PATCH 2/6] memory: tegra114-emc: Use the full DRAM bus width for interconnect requests Patrick Fischer via B4 Relay
2026-11-11 10:10 ` [PATCH 3/6] memory: tegra114-emc: Always restore the auto-calibration interval Patrick Fischer via B4 Relay
2026-11-11 10:10 ` [PATCH 4/6] dt-bindings: memory: tegra: Add Tegra114 EMC channel registers Patrick Fischer via B4 Relay
2026-11-11 10:24   ` sashiko-bot [this message]
2026-11-11 10:11 ` [PATCH 5/6] memory: tegra114-emc: Program pad auto-calibration per channel Patrick Fischer via B4 Relay
2026-11-11 10:11 ` [PATCH 6/6] ARM: tegra: Add EMC channel registers on Tegra114 Patrick Fischer via B4 Relay

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=sashiko-outbox-208800@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=admin@tsv-stahl-riesa.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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