From: Conor Dooley <conor@kernel.org>
To: Sean Anderson <sean.anderson@linux.dev>
Cc: "Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Richard Alpe" <richard@bit42.se>,
linux-kernel@vger.kernel.org,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Michael Walle" <michael@walle.cc>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: Remove fsl,t1023-sfp in favor of fsl,layerscape-sfp
Date: Sun, 17 Mar 2024 15:10:50 +0000 [thread overview]
Message-ID: <20240317-starved-pager-7a81c5045cfc@spud> (raw)
In-Reply-To: <20240316002026.1808336-1-sean.anderson@linux.dev>
[-- Attachment #1: Type: text/plain, Size: 3191 bytes --]
On Fri, Mar 15, 2024 at 08:20:25PM -0400, Sean Anderson wrote:
> These bindings document the same hardware (just different minor
> revisions). Remove the newer fsl,t1023-sfp.
>
> Fixes: aa1ed6047107 ("dt-bindings: nvmem: Add t1023-sfp efuse support")
> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
> ---
>
> .../bindings/nvmem/fsl,layerscape-sfp.yaml | 21 ++++++++++-
> .../bindings/nvmem/fsl,t1023-sfp.yaml | 37 -------------------
> 2 files changed, 19 insertions(+), 39 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/nvmem/fsl,t1023-sfp.yaml
>
> diff --git a/Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml b/Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml
> index 70fb2ad25103..8a54dd1328ea 100644
> --- a/Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml
> @@ -19,6 +19,13 @@ allOf:
> properties:
> compatible:
> oneOf:
> + - description: Trust architecture 2.0 SFP
> + items:
> + enum:
> + - fsl,t1023-sfp
> + - fsl,t1040-sfp
> + - fsl,t2080-sfp
> + - fsl,t4240-sfp
You should at least mention where these three compatibles came from,
given they were not documented in t1023-sfp.yaml. Additionally, should
they fall back to t1023-sfp? I see that there's already some dts files
with these compatibles in them but seemingly no driver support as there
is for the t1023-sfp.
Cheers,
Conor.
> - description: Trust architecture 2.1 SFP
> items:
> - const: fsl,ls1021a-sfp
> @@ -45,8 +52,18 @@ properties:
> required:
> - compatible
> - reg
> - - clock-names
> - - clocks
> +
> +if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - fsl,ls1021a-sfp
> + - fsl,ls1028a-sfp
> +then:
> + required:
> + - clocks
> + - clock-names
>
> unevaluatedProperties: false
>
> diff --git a/Documentation/devicetree/bindings/nvmem/fsl,t1023-sfp.yaml b/Documentation/devicetree/bindings/nvmem/fsl,t1023-sfp.yaml
> deleted file mode 100644
> index df826b40d8ca..000000000000
> --- a/Documentation/devicetree/bindings/nvmem/fsl,t1023-sfp.yaml
> +++ /dev/null
> @@ -1,37 +0,0 @@
> -# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> -%YAML 1.2
> ----
> -$id: http://devicetree.org/schemas/nvmem/fsl,t1023-sfp.yaml#
> -$schema: http://devicetree.org/meta-schemas/core.yaml#
> -
> -title: NXP QorIQ eFuse support
> -
> -maintainers:
> - - Richard Alpe <richard@bit42.se>
> -
> -description:
> - Read support for the eFuses (SFP) on NXP QorIQ series SoC's.
> -
> -allOf:
> - - $ref: nvmem.yaml#
> -
> -properties:
> - compatible:
> - const: fsl,t1023-sfp
> -
> - reg:
> - maxItems: 1
> -
> -required:
> - - compatible
> - - reg
> -
> -unevaluatedProperties: false
> -
> -examples:
> - - |
> - efuse@e8000 {
> - compatible = "fsl,t1023-sfp";
> - reg = <0xe8000 0x1000>;
> - };
> -...
> --
> 2.35.1.1320.gc452695387.dirty
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-03-17 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 0:20 [PATCH 1/2] dt-bindings: nvmem: Remove fsl,t1023-sfp in favor of fsl,layerscape-sfp Sean Anderson
2024-03-17 15:10 ` Conor Dooley [this message]
2024-03-18 15:08 ` Sean Anderson
2024-03-18 15:40 ` Conor Dooley
2024-03-18 15:48 ` Sean Anderson
2024-03-19 17:55 ` Conor Dooley
2024-03-21 16:21 ` Sean Anderson
2024-03-22 7:01 ` Krzysztof Kozlowski
2024-03-22 16:26 ` Sean Anderson
2024-03-22 18:14 ` Conor Dooley
2024-03-22 18:26 ` Sean Anderson
2024-03-17 21:12 ` Rob Herring
2024-03-18 8:16 ` richard
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=20240317-starved-pager-7a81c5045cfc@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=niklas.soderlund@ragnatech.se \
--cc=richard@bit42.se \
--cc=robh+dt@kernel.org \
--cc=sean.anderson@linux.dev \
--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