From: Michael Walle <michael@walle.cc>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Sean Anderson <sean.anderson@seco.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Li Yang <leoyang.li@nxp.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v3 0/9] nvmem: sfp: binding updates and additions
Date: Mon, 09 May 2022 10:28:09 +0200 [thread overview]
Message-ID: <8602f6adb0fcf591e2923c736b345abd@walle.cc> (raw)
In-Reply-To: <3b8fc56f64508f7604f3b9e14b048568@walle.cc>
Am 2022-05-03 15:43, schrieb Michael Walle:
> Am 2022-04-29 17:56, schrieb Srinivas Kandagatla:
>> On 28/04/2022 19:16, 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.
>>>
>>> I would like to get this series merged for 5.18. As noted in patch 2,
>>> making the clock property mandatory is not an ABI break, but if this
>>> is
>>> not applied then it would become an ABI break. The absolute minimum
>>> patches to apply for this would be patches 2 and 5. The rest
>>> (including
>>> the regmap changes) could be deferred if necessary.
>>>
>>> [1]
>>> https://lore.kernel.org/u-boot/7c8e206a-cd40-2a77-6282-7f4bead2b13a@seco.com/T/#m591f8425b6f096ab3d54e6f7bd258e41cfa4c43b
>>>
>>> Changes in v3:
>>> - Update commit message to note that this binding has not yet been
>>> present in a relase, so it is OK to make otherwise breaking
>>> changes.
>>>
>>> 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
>>>
>>
>> I have applied all the patches except 5/9, 6/9, and 7/9 dts patches
>> which need to go via dts maintainer tree.
>
> Ahh. At least the device tree binding change (and the device tree
> changes itself) should be applied as fixes for the 5.18 release,
> so we don't have any conflicting descriptions. My fixes tag was never
> picked up, unfortunately:
> https://lore.kernel.org/linux-devicetree/4a45db184fbadc278624571dfbeb5004@walle.cc/
>
> Srinivas, I've seen you picked it up into your for-next branch.
> Can we fix that?
>
> I'd guess the layerscape device tree change also need a Fixes: tag.
Ping. We are now -rc7 :/
-michael
prev parent reply other threads:[~2022-05-09 8:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 18:16 [PATCH v3 0/9] nvmem: sfp: binding updates and additions Sean Anderson
2022-04-28 18:16 ` [PATCH v3 1/9] dt-bindings: nvmem: sfp: Fix typo Sean Anderson
2022-04-28 18:16 ` [PATCH v3 2/9] dt-bindings: nvmem: sfp: Add clock properties Sean Anderson
2022-04-28 18:16 ` [PATCH v3 3/9] dt-bindings: nvmem: sfp: Add TA_PROG_SFP supply Sean Anderson
2022-04-28 18:16 ` [PATCH v3 4/9] dt-bindings: nvmem: sfp: Add compatible binding for TA 2.1 SFPs Sean Anderson
2022-04-28 18:16 ` [PATCH v3 5/9] arm64: dts: ls1028a: Update SFP binding to include clock Sean Anderson
2022-05-03 13:47 ` Michael Walle
2022-06-29 13:32 ` Shawn Guo
2022-04-28 18:17 ` [PATCH v3 6/9] ARM: dts: layerscape: Add SFP binding for TA 2.1 devices Sean Anderson
2022-06-29 13:34 ` Shawn Guo
2022-04-28 18:17 ` [PATCH v3 7/9] ARM: dts: Add SFP binding for TA 3.0 devices Sean Anderson
2022-04-28 18:17 ` [PATCH v3 8/9] nvmem: sfp: Use regmap Sean Anderson
2022-04-28 18:17 ` [PATCH v3 9/9] nvmem: sfp: Add support for TA 2.1 devices Sean Anderson
2022-04-29 15:56 ` [PATCH v3 0/9] nvmem: sfp: binding updates and additions Srinivas Kandagatla
2022-05-03 13:43 ` Michael Walle
2022-05-09 8:28 ` Michael Walle [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=8602f6adb0fcf591e2923c736b345abd@walle.cc \
--to=michael@walle.cc \
--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=robh+dt@kernel.org \
--cc=sean.anderson@seco.com \
--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).