Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Christian Marangi" <ansuelsmth@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: nvmem: airoha: add SMC eFuses schema
Date: Tue, 19 May 2026 16:12:28 +0000	[thread overview]
Message-ID: <20260519161228.C37FAC2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260519152807.29407-2-ansuelsmth@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The schema is missing the compatible string for the Airoha AN7583 SoC, despite it being explicitly mentioned in the commit message.
--

commit 4691b687a514217a385c7b7725536b71c206a6c2
Author: Christian Marangi <ansuelsmth@gmail.com>

dt-bindings: nvmem: airoha: add SMC eFuses schema

This commit adds a new device tree binding schema for the Airoha SMC
eFuses. It documents the access method for the eFuse banks via SMC
commands for the new Airoha SoCs.

> Add Airoha SMC eFuses schema to document new Airoha SoC AN7581/AN7583
> way of accessing the 2 eFuse bank via the SMC command.

[Severity: Medium]
Is the AN7583 SoC supposed to be included in the schema? The commit
message mentions both AN7581 and AN7583, but the schema below only documents
the AN7581.

> diff --git a/Documentation/devicetree/bindings/nvmem/airoha,smc-efuses.yaml b/Documentation/devicetree/bindings/nvmem/airoha,smc-efuses.yaml
> new file mode 100644
> index 0000000000000..c52f8d4bec392
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/airoha,smc-efuses.yaml
[ ... ]
> +title: Airoha SMC eFuses
> +
> +description: |
> +  Airoha new SoC AN7581 expose banks of eFuse accessible
> +  via specific SMC commands.

[Severity: Medium]
Should AN7583 also be mentioned in the description here to match the
details in the commit message?

[ ... ]
> +properties:
> +  compatible:
> +    enum:
> +      - airoha,an7581-efuses

[Severity: Medium]
Should airoha,an7583-efuses be included in this enum if the binding is
intended to support the AN7583 SoC? 

If AN7583 uses this block, omitting its specific compatible string might
cause device tree validation to fail for valid AN7583 device trees.

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260519152807.29407-1-ansuelsmth@gmail.com?part=1

  reply	other threads:[~2026-05-19 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 15:28 [PATCH v4 0/2] nvmem: airoha: Add support for SMC eFUSE Christian Marangi
2026-05-19 15:28 ` [PATCH v4 1/2] dt-bindings: nvmem: airoha: add SMC eFuses schema Christian Marangi
2026-05-19 16:12   ` sashiko-bot [this message]
2026-05-19 15:28 ` [PATCH v4 2/2] nvmem: airoha: Add support for SMC eFUSE Christian Marangi
2026-05-19 15:40 ` [PATCH v4 0/2] " Srinivas Kandagatla

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=20260519161228.C37FAC2BCB3@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ansuelsmth@gmail.com \
    --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