From: Rob Herring <robh@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
Li Yang <leoyang.li@nxp.com>, Rob Herring <robh+dt@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH v1 1/3] dt-bindings: nvmem: add fsl,layerscape-sfp binding
Date: Fri, 11 Feb 2022 06:52:29 -0600 [thread overview]
Message-ID: <YgZcDd+xwXqTVlAv@robh.at.kernel.org> (raw)
In-Reply-To: <20220127163728.3650648-2-michael@walle.cc>
On Thu, 27 Jan 2022 17:37:26 +0100, Michael Walle wrote:
> The Security Fuse Processor provides efuses and is responsible for
> reading it at SoC startup and configuring it accordingly.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> .../bindings/nvmem/fsl,layerscape-sfp.yaml | 38 +++++++++++++++++++
> 1 file changed, 38 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-11 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 16:37 [PATCH v1 0/3] nvmem: add Layerscape SFP support Michael Walle
2022-01-27 16:37 ` [PATCH v1 1/3] dt-bindings: nvmem: add fsl,layerscape-sfp binding Michael Walle
2022-02-11 12:52 ` Rob Herring [this message]
2022-01-27 16:37 ` [PATCH v1 2/3] nvmem: add driver for Layerscape SFP (Security Fuse Processor) Michael Walle
2022-02-14 10:58 ` Srinivas Kandagatla
2022-01-27 16:37 ` [PATCH v1 3/3] arm64: dts: ls1028a: add efuse node Michael Walle
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=YgZcDd+xwXqTVlAv@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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