Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Pinkesh Vaghela" <pinkesh.vaghela@einfochips.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 4/8] dt-bindings: mfd: syscon: add ESWIN EIC7700 compatible
Date: Tue, 04 Aug 2026 11:02:06 +0000	[thread overview]
Message-ID: <20260804110206.E4BF31F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260804104431.1391839-5-pinkesh.vaghela@einfochips.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The new compatible string 'eswin,eic7700-syscfg' was omitted from the 'select' block's enum list in `syscon.yaml`.
- [Low] The commit message description is not capitalized, violating MFD subsystem guidelines.
--

--- Patch [4]: [PATCH v3 4/8] dt-bindings: mfd: syscon: add ESWIN EIC7700 compatible ---
commit b6fbe8a9c92251f8d7a4c290284000e71004ed87
Author: Pinkesh Vaghela <pinkesh.vaghela@einfochips.com>

dt-bindings: mfd: syscon: add ESWIN EIC7700 compatible
    
Document ESWIN EIC7700 SoC compatible for syscon registers.

> dt-bindings: mfd: syscon: add ESWIN EIC7700 compatible

[Severity: Low]
This isn't a bug, but should the commit description be capitalized after 
the subsystem prefix to match MFD subsystem guidelines, perhaps using 
"Add ESWIN EIC7700 compatible"?

[ ... ]

> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml
> index e228670880631..2bcaaba6948d3 100644
> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml
> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml
> @@ -175,6 +175,7 @@ properties:
>                - cirrus,ep7209-syscon3
>                - cnxt,cx92755-uc
>                - econet,en751221-chip-scu
> +              - eswin,eic7700-syscfg

[Severity: Medium]
Does this new compatible string also need to be mirrored in the select 
block's enum list earlier in the file?

If eswin,eic7700-syscfg is omitted from the select list:

  select:
    properties:
      compatible:
        contains:
          enum:
            ...
            - econet,en751221-chip-scu
            - freecom,fsg-cs2-system-controller

will older tooling like dtschema < 2024.02 fail to select this schema as a
fallback, which could silently allow invalid configurations to pass undetected?

>                - freecom,fsg-cs2-system-controller
>                - fsl,imx93-aonmix-ns-syscfg
>                - fsl,imx93-wakeupmix-syscfg

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260804104431.1391839-1-pinkesh.vaghela@einfochips.com?part=4

  reply	other threads:[~2026-08-04 11:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 10:44 [PATCH v3 0/8] riscv: eswin: eic7700: Add support for clocks, resets, pinctrl, HSP bus, I2C and watchdog Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 1/8] riscv: dts: eswin: add reset generator for EIC7700 SoC Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 2/8] riscv: dts: eswin: add clock " Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 3/8] riscv: dts: eswin: eic7700: add pinctrl support Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 4/8] dt-bindings: mfd: syscon: add ESWIN EIC7700 compatible Pinkesh Vaghela
2026-08-04 11:02   ` sashiko-bot [this message]
2026-08-04 13:26     ` Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 5/8] riscv: dts: eswin: add hsp bus node Pinkesh Vaghela
2026-08-04 11:12   ` sashiko-bot
2026-08-04 13:07     ` Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 6/8] dt-bindings: i2c: dw: add ESWIN EIC7700 SoC I2C controller Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 7/8] riscv: dts: eswin: add I2C controller support Pinkesh Vaghela
2026-08-04 11:22   ` sashiko-bot
2026-08-04 13:19     ` Pinkesh Vaghela
2026-08-04 10:44 ` [PATCH v3 8/8] riscv: dts: eswin: add watchdog support Pinkesh Vaghela
2026-08-04 11:34   ` sashiko-bot
2026-08-04 13:03     ` Pinkesh Vaghela

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=20260804110206.E4BF31F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=pinkesh.vaghela@einfochips.com \
    --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