From: "Rob Herring (Arm)" <robh@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: nvmem: airoha: add SMC eFuses schema
Date: Mon, 21 Jul 2025 15:18:08 -0500 [thread overview]
Message-ID: <175312908728.1269914.10346607252640747468.robh@kernel.org> (raw)
In-Reply-To: <20250721184640.2885-1-ansuelsmth@gmail.com>
On Mon, 21 Jul 2025 20:46:33 +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>
> ---
> Changes v2:
> - Drop redundant description for reg
> - Improve example node name
>
> .../bindings/nvmem/airoha,smc-efuses.yaml | 65 +++++++++++++++++++
> 1 file changed, 65 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/airoha,smc-efuses.yaml
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-07-21 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 18:46 [PATCH v2 1/2] dt-bindings: nvmem: airoha: add SMC eFuses schema Christian Marangi
2025-07-21 18:46 ` [PATCH v2 2/2] nvmem: airoha: Add support for SMC eFUSE Christian Marangi
2025-07-21 20:18 ` Rob Herring (Arm) [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-07 16:13 [PATCH v2 0/2] " Christian Marangi
2025-11-07 16:13 ` [PATCH v2 1/2] dt-bindings: nvmem: airoha: add SMC eFuses schema Christian Marangi
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=175312908728.1269914.10346607252640747468.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