From: Rob Herring <robh@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: airoha: add SMC eFuses schema
Date: Mon, 14 Jul 2025 22:52:33 -0500 [thread overview]
Message-ID: <20250715035233.GA7855-robh@kernel.org> (raw)
In-Reply-To: <20250714151349.28368-1-ansuelsmth@gmail.com>
On Mon, Jul 14, 2025 at 05:13:46PM +0200, Christian Marangi wrote:
> Add Airoha SMC eFuses schema to document new Airoha SoC AN7581/AN7583
> way of accessing the 2 eFuse bank via the SMC command.
>
> Each eFuse bank expose 64 eFuse cells of 32 bit used to give information
> on HW Revision, PHY Calibration, Device Model, Private Key and
> all kind of other info specific to the SoC or the running system.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> .../bindings/nvmem/airoha,smc-efuses.yaml | 65 +++++++++++++++++++
> 1 file changed, 65 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/airoha,smc-efuses.yaml
>
> 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 000000000000..399c3c14f6ea
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/airoha,smc-efuses.yaml
> @@ -0,0 +1,65 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/nvmem/airoha,smc-efuses.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Airoha SMC eFuses
> +
> +description: |
> + Airoha new SoC (AN7581/AN7583) expose banks of eFuse accessible
> + via specific SMC commands.
> +
> + 2 different bank of eFuse or 64 cells of 32 bit are exposed
> + read-only used to give information on HW Revision, PHY Calibration,
> + Device Model, Private Key...
> +
> +maintainers:
> + - Christian Marangi <ansuelsmth@gmail.com>
> +
> +properties:
> + compatible:
> + enum:
> + - airoha,an7581-efuses
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 0
> +
> +patternProperties:
> + '^efuse-bank@[0-1]$':
> + type: object
> +
> + allOf:
> + - $ref: nvmem.yaml#
> +
> + properties:
> + reg:
> + description: Identify the eFuse bank. (0 or 1)
Drop "(0 or 1)". You say that here:
> + enum: [0, 1]
> +
> + required:
> + - reg
> +
> + unevaluatedProperties: false
> +
> +required:
> + - compatible
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + airoha-efuses {
efuse {
And put this under a /firmware node (not here, but in your .dts).
> + compatible = "airoha,an7581-efuses";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + efuse-bank@0 {
> + reg = <0>;
> + };
> + };
> +
> +...
> --
> 2.48.1
>
prev parent reply other threads:[~2025-07-15 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 15:13 Christian Marangi
2025-07-14 15:13 ` [PATCH 2/2] nvmem: airoha: Add support for SMC eFUSE Christian Marangi
2025-07-15 3:52 ` Rob Herring [this message]
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=20250715035233.GA7855-robh@kernel.org \
--to=robh@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
/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
all inboxes | Powered by JetHome®