From: Sean Anderson <sean.anderson@seco.com>
To: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>, Rob Herring <robh+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
linux-kernel@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Li Yang <leoyang.li@nxp.com>, Michael Walle <michael@walle.cc>
Subject: Re: [PATCH v2 0/9] nvmem: sfp: binding updates and additions
Date: Fri, 22 Apr 2022 10:54:28 -0400 [thread overview]
Message-ID: <9ec1e889-178f-9b99-c73a-9f31c6c99563@seco.com> (raw)
In-Reply-To: <20220422145147.2210587-1-sean.anderson@seco.com>
On 4/22/22 10:51 AM, Sean Anderson wrote:
> This adds several properties to the Layerscape Security Fuse Processor
> (SFP) necessary for writing. Although the Linux driver does not use
> these bindings, I plan to use them in U-Boot [1]. It also adds a new
> compatibles for Trust Architecture (TA) 2.1 devices. In addition, it
> also adds an SFP binding for all TA 2.1 and 3.0 devices.
>
> [1] https://lore.kernel.org/u-boot/7c8e206a-cd40-2a77-6282-7f4bead2b13a@seco.com/T/#m591f8425b6f096ab3d54e6f7bd258e41cfa4c43b
>
> Changes in v2:
> - Mention "regulator" in the description for ta-prog-sfp-supply
> - Convert sfp driver to use regmap
> - Fix various typos in commit messages
>
> Sean Anderson (9):
> dt-bindings: nvmem: sfp: Fix typo
> dt-bindings: nvmem: sfp: Add clock properties
> dt-bindings: nvmem: sfp: Add TA_PROG_SFP supply
> dt-bindings: nvmem: sfp: Add compatible binding for TA 2.1 SFPs
> arm64: dts: ls1028a: Update SFP binding to include clock
> ARM: dts: layerscape: Add SFP binding for TA 2.1 devices
> ARM: dts: Add SFP binding for TA 3.0 devices
> nvmem: sfp: Use regmap
> nvmem: sfp: Add support for TA 2.1 devices
>
> .../bindings/nvmem/fsl,layerscape-sfp.yaml | 30 ++++++++++++++--
> arch/arm/boot/dts/ls1021a.dtsi | 7 ++++
> .../arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 8 +++++
> .../arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 5 ++-
> .../arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 8 +++++
> .../arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 8 +++++
> .../arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 8 +++++
> .../arm64/boot/dts/freescale/fsl-ls208xa.dtsi | 8 +++++
> .../arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 8 +++++
> drivers/nvmem/Kconfig | 1 +
> drivers/nvmem/layerscape-sfp.c | 36 ++++++++++++++-----
> 11 files changed, 115 insertions(+), 12 deletions(-)
>
I forgot to pick up Reviewed-bys from v1. I can resend this or add them for v3.
--Sean
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-22 15:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 14:51 [PATCH v2 0/9] nvmem: sfp: binding updates and additions Sean Anderson
2022-04-22 14:51 ` [PATCH v2 1/9] dt-bindings: nvmem: sfp: Fix typo Sean Anderson
2022-04-22 14:51 ` [PATCH v2 2/9] dt-bindings: nvmem: sfp: Add clock properties Sean Anderson
2022-04-22 21:10 ` Rob Herring
2022-04-22 14:51 ` [PATCH v2 3/9] dt-bindings: nvmem: sfp: Add TA_PROG_SFP supply Sean Anderson
2022-04-22 15:02 ` Andrew Lunn
2022-04-22 14:51 ` [PATCH v2 4/9] dt-bindings: nvmem: sfp: Add compatible binding for TA 2.1 SFPs Sean Anderson
2022-04-22 14:51 ` [PATCH v2 5/9] arm64: dts: ls1028a: Update SFP binding to include clock Sean Anderson
2022-04-22 14:51 ` [PATCH v2 6/9] ARM: dts: layerscape: Add SFP binding for TA 2.1 devices Sean Anderson
2022-04-22 14:51 ` [PATCH v2 7/9] ARM: dts: Add SFP binding for TA 3.0 devices Sean Anderson
2022-04-22 14:51 ` [PATCH v2 8/9] nvmem: sfp: Use regmap Sean Anderson
2022-04-22 14:51 ` [PATCH v2 9/9] nvmem: sfp: Add support for TA 2.1 devices Sean Anderson
2022-04-22 14:54 ` Sean Anderson [this message]
2022-04-22 15:01 ` [PATCH v2 0/9] nvmem: sfp: binding updates and additions Andrew Lunn
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=9ec1e889-178f-9b99-c73a-9f31c6c99563@seco.com \
--to=sean.anderson@seco.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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;
as well as URLs for NNTP newsgroup(s).