[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231127182408.GA2131525-robh@kernel.org>
Date: Mon, 27 Nov 2023 12:24:08 -0600
From: Rob Herring <robh@...nel.org>
To: Jisheng Zhang <jszhang@...nel.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
Chao Wei <chao.wei@...hgo.com>,
Chen Wang <unicorn_wang@...look.com>
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: Add sophgo,efuses
On Sun, Nov 19, 2023 at 09:13:31PM +0800, Jisheng Zhang wrote:
> Sophgo SoCs such as CV1800B come with eFuses used to store
> factory-programmed data such as calibration settings for the built-in
> ethernet PHY.
>
> Signed-off-by: Jisheng Zhang <jszhang@...nel.org>
> ---
> .../bindings/nvmem/sophgo,efuse.yaml | 54 +++++++++++++++++++
> 1 file changed, 54 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/sophgo,efuse.yaml
>
> diff --git a/Documentation/devicetree/bindings/nvmem/sophgo,efuse.yaml b/Documentation/devicetree/bindings/nvmem/sophgo,efuse.yaml
> new file mode 100644
> index 000000000000..e4ae81a1742a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/sophgo,efuse.yaml
> @@ -0,0 +1,54 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/nvmem/sophgo,efuse.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Sophgo SoC eFuse-based NVMEM
> +
> +description: |
> + Sophgo SoCs such as the CV1800B contain factory-programmed eFuses used to e.g. store
> + calibration data for the built-in ethernet PHY.
> +maintainers:
> + - Jisheng Zhang <jszhang@...nel.org>
> +
> +allOf:
> + - $ref: nvmem.yaml#
> + - $ref: nvmem-deprecated-cells.yaml#
Why does a new binding need to use the deprecated form?
Rob
Powered by blists - more mailing lists