Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Caleb James DeLisle" <cjd@cjdns.fr>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
	krzk+dt@kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: PCI: mediatek: Add support for EcoNet EN7528
Date: Thu, 14 May 2026 10:39:58 +0000	[thread overview]
Message-ID: <20260514104000.02853C2BCB8@smtp.kernel.org> (raw)
In-Reply-To: <20260513191652.3200607-2-cjd@cjdns.fr>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The conditional block for `econet,en7528-pcie` uses `reset: false` instead of `resets: false`, failing to correctly forbid the standard `resets` property.
--

commit 31e1455525e7bb47d92cbe65ee706b4484b25676
Author: Caleb James DeLisle <cjd@cjdns.fr>

dt-bindings: PCI: mediatek: Add support for EcoNet EN7528

This commit introduces the EcoNet EN7528 SoC compatible string to the
MediaTek PCIe controller binding and adds a conditional block to define
its specific property constraints.

> diff --git a/Documentation/devicetree/bindings/pci/mediatek-pcie.yaml b/Documentation/devicetree/bindings/pci/mediatek-pcie.yaml
> --- a/Documentation/devicetree/bindings/pci/mediatek-pcie.yaml
> +++ b/Documentation/devicetree/bindings/pci/mediatek-pcie.yaml
[ ... ]
> @@ -226,6 +227,31 @@ allOf:
>  
>          mediatek,pbus-csr: false
>  
> +  - if:
> +      properties:
> +        compatible:
> +          contains:
> +            const: econet,en7528-pcie
> +    then:
> +      properties:
> +        clocks:
> +          maxItems: 1
> +
> +        clock-names:
> +          maxItems: 1
> +
> +        reset: false

Should this be resets (plural) instead of reset?

The standard property for hardware reset lines is resets. Setting reset to
false will fail to override the global definition, which means the schema 
might inadvertently allow the resets property instead of strictly forbidding
it for this hardware variant.

> +
> +        reset-names: false
> +
> +        power-domains: false
> +
> +        mediatek,pbus-csr: false
> +
> +      required:
> +        - phys
> +        - phy-names
> +
>  unevaluatedProperties: false

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260513191652.3200607-1-cjd@cjdns.fr?part=1

  reply	other threads:[~2026-05-14 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 19:16 [PATCH v6 0/2] Add EcoNet EN7528 (and EN751221) PCIe support Caleb James DeLisle
2026-05-13 19:16 ` [PATCH v6 1/2] dt-bindings: PCI: mediatek: Add support for EcoNet EN7528 Caleb James DeLisle
2026-05-14 10:39   ` sashiko-bot [this message]
2026-05-13 19:16 ` [PATCH v6 2/2] PCI: mediatek: Add support for EcoNet EN7528 SoC Caleb James DeLisle
2026-05-13 21:07   ` Bjorn Helgaas
2026-05-13 21:39     ` Caleb James DeLisle
2026-05-13 22:06       ` Bjorn Helgaas
2026-05-13 22:17         ` Caleb James DeLisle
2026-05-14 11:35   ` sashiko-bot
2026-05-14 12:32     ` Caleb James DeLisle

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=20260514104000.02853C2BCB8@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=cjd@cjdns.fr \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-pci@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