All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Alexey Charkov" <alchark@flipper.net>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 2/4] dt-bindings: nvmem: layouts: Add Rockchip OTP CPUID layout
Date: Wed, 02 Sep 2026 13:15:26 +0000	[thread overview]
Message-ID: <20260902131526.A3A941F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260902-rk3576-otp-cpuid-mac-v2-2-e4b7fe2ab13f@flipper.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The 'mac-address' NVMEM cell node provides phandle arguments but omits '#nvmem-cell-cells' from its required list.
--

commit fcf6d128e83a760e02cdd15150b742b14d86fe0d
Author: Alexey Charkov <alchark@flipper.net>

dt-bindings: nvmem: layouts: Add Rockchip OTP CPUID layout

This commit introduces a new NVMEM layout binding for the Rockchip OTP CPU ID.
It describes how the CPU ID is used to derive a stable Ethernet MAC address
and provides the corresponding device tree schema.

> diff --git a/Documentation/devicetree/bindings/nvmem/layouts/rockchip,rk3576-otp-cpuid.yaml b/Documentation/devicetree/bindings/nvmem/layouts/rockchip,rk3576-otp-cpuid.yaml
> new file mode 100644
> index 0000000000000..85153d480950a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/layouts/rockchip,rk3576-otp-cpuid.yaml
[ ... ]
> +properties:
> +  compatible:
> +    const: rockchip,rk3576-otp-cpuid
> +
> +  mac-address:
> +    type: object
> +    description:
> +      MAC address derived from the CPU ID. The first argument of the phandle
> +      selects one of the two addresses that can be derived (can be 0 or 1).
> +
> +    properties:
> +      "#nvmem-cell-cells":
> +        const: 1
> +
> +    additionalProperties: false

[Severity: Medium]
Since the mac-address NVMEM cell node provides phandle arguments and defines
#nvmem-cell-cells, should it also be included in a required list for this
node to enforce its presence?

Without this, incomplete mac-address nodes in device trees might silently
pass dt-schema validation but fail at runtime when the kernel attempts to
parse the NVMEM cell phandle arguments.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260902-rk3576-otp-cpuid-mac-v2-0-e4b7fe2ab13f@flipper.net?part=2

  reply	other threads:[~2026-09-02 13:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 13:07 [PATCH v2 0/4] nvmem: Derive Rockchip MAC addresses from the OTP CPU ID Alexey Charkov
2026-09-02 13:07 ` Alexey Charkov
2026-09-02 13:07 ` [PATCH v2 1/4] nvmem: rockchip-otp: Serialize reads Alexey Charkov
2026-09-02 13:07   ` Alexey Charkov
2026-09-02 13:07 ` [PATCH v2 2/4] dt-bindings: nvmem: layouts: Add Rockchip OTP CPUID layout Alexey Charkov
2026-09-02 13:07   ` Alexey Charkov
2026-09-02 13:15   ` sashiko-bot [this message]
2026-09-02 13:07 ` [PATCH v2 3/4] nvmem: layouts: Add Rockchip OTP CPUID layout driver Alexey Charkov
2026-09-02 13:07   ` Alexey Charkov
2026-09-02 13:20   ` sashiko-bot
2026-09-14 22:23   ` Srinivas Kandagatla
2026-09-14 22:23     ` Srinivas Kandagatla
2026-09-02 13:07 ` [PATCH v2 4/4] arm64: dts: rockchip: Derive GMAC MAC addresses from OTP on RK3576 Alexey Charkov
2026-09-02 13:07   ` Alexey Charkov
2026-09-10 14:48 ` [PATCH v2 0/4] nvmem: Derive Rockchip MAC addresses from the OTP CPU ID Alexey Charkov
2026-09-10 14:48   ` Alexey Charkov
2026-09-17 22:18   ` Rob Herring
2026-09-17 22:18     ` Rob Herring
2026-09-18  7:08     ` Alexey Charkov
2026-09-18  7:08       ` Alexey Charkov
2026-09-10 16:49 ` Ricardo Pardini
2026-09-10 16:49   ` Ricardo Pardini
2026-09-14 22:13 ` (subset) " Srinivas Kandagatla
2026-09-14 22:13   ` 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=20260902131526.A3A941F00A3D@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alchark@flipper.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.