From: Rob Herring <robh@kernel.org>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
Subject: Re: [PATCH 10/14] dt-bindings: reset: snps,hsdk-reset: Convert to yaml
Date: Fri, 8 Apr 2022 16:12:08 -0500 [thread overview]
Message-ID: <YlClKKHnTwsNUayj@robh.at.kernel.org> (raw)
In-Reply-To: <20220407154338.4190674-10-p.zabel@pengutronix.de>
On Thu, Apr 07, 2022 at 05:43:34PM +0200, Philipp Zabel wrote:
> Convert the device tree bindings for the Synopsys HSDK reset controller
> to YAML schema to allow participating in DT validation.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Cc: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
> ---
> .../bindings/reset/snps,hsdk-reset.txt | 28 -----------
> .../bindings/reset/snps,hsdk-reset.yaml | 47 +++++++++++++++++++
> 2 files changed, 47 insertions(+), 28 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/reset/snps,hsdk-reset.txt
> create mode 100644 Documentation/devicetree/bindings/reset/snps,hsdk-reset.yaml
>
> diff --git a/Documentation/devicetree/bindings/reset/snps,hsdk-reset.txt b/Documentation/devicetree/bindings/reset/snps,hsdk-reset.txt
> deleted file mode 100644
> index 830069b1c37c..000000000000
> --- a/Documentation/devicetree/bindings/reset/snps,hsdk-reset.txt
> +++ /dev/null
> @@ -1,28 +0,0 @@
> -Binding for the Synopsys HSDK reset controller
> -
> -This binding uses the common reset binding[1].
> -
> -[1] Documentation/devicetree/bindings/reset/reset.txt
> -
> -Required properties:
> -- compatible: should be "snps,hsdk-reset".
> -- reg: should always contain 2 pairs address - length: first for reset
> - configuration register and second for corresponding SW reset and status bits
> - register.
> -- #reset-cells: from common reset binding; Should always be set to 1.
> -
> -Example:
> - reset: reset@880 {
> - compatible = "snps,hsdk-reset";
> - #reset-cells = <1>;
> - reg = <0x8A0 0x4>, <0xFF0 0x4>;
> - };
> -
> -Specifying reset lines connected to IP modules:
> - ethernet@.... {
> - ....
> - resets = <&reset HSDK_V1_ETH_RESET>;
> - ....
> - };
> -
> -The index could be found in <dt-bindings/reset/snps,hsdk-reset.h>
> diff --git a/Documentation/devicetree/bindings/reset/snps,hsdk-reset.yaml b/Documentation/devicetree/bindings/reset/snps,hsdk-reset.yaml
> new file mode 100644
> index 000000000000..a7cb5580c070
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/reset/snps,hsdk-reset.yaml
> @@ -0,0 +1,47 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/reset/snps,hsdk-reset.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Synopsys HSDK reset controller
> +
> +maintainers:
> + - Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
> +
> +properties:
> + compatible:
> + const: snps,hsdk-reset
> +
> + reg:
> + minItems: 2
> + maxItems: 2
> + description: |
> + Should always contain 2 pairs address - length: first for reset
> + configuration register and second for corresponding SW reset and status
> + bits register.
items:
- description: reset configuration register
- description: corresponding SW reset and status bits register
> +
> + '#reset-cells':
> + const: 1
> +
> +required:
> + - compatible
> + - reg
> + - '#reset-cells'
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/reset/snps,hsdk-reset.h>
> +
> + reset: reset@880 {
> + compatible = "snps,hsdk-reset";
> + #reset-cells = <1>;
> + reg = <0x8A0 0x4>, <0xFF0 0x4>;
> + };
> +
> + // Specifying reset lines connected to IP modules:
> + ethernet {
> + resets = <&reset HSDK_ETH_RESET>;
> + };
No need to show the consumer side in every provider. Please drop.
Rob
next prev parent reply other threads:[~2022-04-08 21:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 15:43 [PATCH 01/14] dt-bindings: reset: amlogic,meson-axg-audio-arb: Convert to yaml Philipp Zabel
2022-04-07 15:43 ` [PATCH 02/14] dt-bindings: reset: ath79: " Philipp Zabel
2022-04-08 21:03 ` Rob Herring
2022-04-07 15:43 ` [PATCH 03/14] dt-bindings: reset: berlin: " Philipp Zabel
2022-04-08 21:04 ` Rob Herring
2022-04-07 15:43 ` [PATCH 04/14] dt-bindings: reset: bitmain,bm1880-reset: " Philipp Zabel
2022-04-08 21:05 ` Rob Herring
2022-04-07 15:43 ` [PATCH 05/14] dt-bindings: reset: lantiq,reset: " Philipp Zabel
2022-04-08 21:07 ` Rob Herring
2022-04-18 16:34 ` Martin Blumenstingl
2022-05-02 15:39 ` Philipp Zabel
2022-04-07 15:43 ` [PATCH 06/14] dt-bindings: reset: nuvoton,npcm-reset: " Philipp Zabel
2022-04-08 21:08 ` Rob Herring
2022-04-07 15:43 ` [PATCH 07/14] dt-bindings: reset: oxsemi,oxnas-reset: " Philipp Zabel
2022-04-08 15:43 ` Rob Herring
2022-04-07 15:43 ` [PATCH 08/14] dt-bindings: reset: snps,axs10x-reset: " Philipp Zabel
2022-04-08 21:09 ` Rob Herring
2022-04-07 15:43 ` [PATCH 09/14] dt-bindings: reset: snps,dw-reset: " Philipp Zabel
2022-04-08 15:43 ` Rob Herring
2022-04-08 18:25 ` Rob Herring
2022-04-11 13:59 ` Philipp Zabel
2025-01-07 15:22 ` Rob Herring
2022-04-07 15:43 ` [PATCH 10/14] dt-bindings: reset: snps,hsdk-reset: " Philipp Zabel
2022-04-08 21:12 ` Rob Herring [this message]
2022-04-07 15:43 ` [PATCH 11/14] dt-bindings: reset: socfpga: " Philipp Zabel
2022-04-08 21:12 ` Rob Herring
2022-04-07 15:43 ` [PATCH 12/14] dt-bindings: reset: st,sti-picophyreset: " Philipp Zabel
2022-04-08 21:13 ` Rob Herring
2022-04-07 15:43 ` [PATCH 13/14] dt-bindings: reset: st,sti-powerdown: " Philipp Zabel
2022-04-08 21:14 ` Rob Herring
2022-04-07 15:43 ` [PATCH 14/14] dt-bindings: reset: " Philipp Zabel
2022-04-07 20:04 ` Rob Herring
2022-05-05 1:08 ` Stephen Warren
2022-08-25 15:53 ` Rob Herring
2022-08-25 16:17 ` Stephen Warren
2022-04-08 21:03 ` [PATCH 01/14] dt-bindings: reset: amlogic,meson-axg-audio-arb: " Rob Herring
2022-04-18 16:32 ` Martin Blumenstingl
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=YlClKKHnTwsNUayj@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=p.zabel@pengutronix.de \
/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).