From: Michael Walle <michael@walle.cc>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Michael Walle <michael@walle.cc>
Subject: [PATCH v2 0/3] nvmem: add Layerscape SFP support
Date: Mon, 14 Feb 2022 12:55:26 +0100 [thread overview]
Message-ID: <20220214115529.662948-1-michael@walle.cc> (raw)
Add support for the Security Fuse Processor found on Layerscape
SoCs.
changes since v1:
- added Rob's Rb
- cleaned up the include files
- changed the module license to only "GPL"
- fix indendation, split lines longer than 80c
Michael Walle (3):
dt-bindings: nvmem: add fsl,layerscape-sfp binding
nvmem: add driver for Layerscape SFP (Security Fuse Processor)
arm64: dts: ls1028a: add efuse node
.../bindings/nvmem/fsl,layerscape-sfp.yaml | 38 ++++++++
.../arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 11 +++
drivers/nvmem/Kconfig | 12 +++
drivers/nvmem/Makefile | 2 +
drivers/nvmem/layerscape-sfp.c | 89 +++++++++++++++++++
5 files changed, 152 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml
create mode 100644 drivers/nvmem/layerscape-sfp.c
--
2.30.2
next reply other threads:[~2022-02-14 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 11:55 Michael Walle [this message]
2022-02-14 11:55 ` [PATCH v2 1/3] dt-bindings: nvmem: add fsl,layerscape-sfp binding Michael Walle
2022-02-14 11:55 ` [PATCH v2 2/3] nvmem: add driver for Layerscape SFP (Security Fuse Processor) Michael Walle
2022-02-14 11:55 ` [PATCH v2 3/3] arm64: dts: ls1028a: add efuse node Michael Walle
2022-02-21 3:51 ` Shawn Guo
2022-02-14 11:58 ` [PATCH v2 0/3] nvmem: add Layerscape SFP support 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=20220214115529.662948-1-michael@walle.cc \
--to=michael@walle.cc \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®