From: Philipp Zabel <p.zabel@pengutronix.de>
To: Neil Armstrong <narmstrong@baylibre.com>, robh+dt@kernel.org
Cc: linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [RFCv2 4/9] dt-bindings: reset: amlogic,meson-reset: convert to yaml
Date: Tue, 06 Aug 2019 09:41:04 +0200 [thread overview]
Message-ID: <1565077264.4951.4.camel@pengutronix.de> (raw)
In-Reply-To: <20190805120320.32282-5-narmstrong@baylibre.com>
On Mon, 2019-08-05 at 14:03 +0200, Neil Armstrong wrote:
> Now that we have the DT validation in place, let's convert the device tree
> bindings for the Amlogic Reset controller over to a YAML schemas.
>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Let me know if you want me to pick up this patch, otherwise
Acked-by: Philipp Zabel <p.zabel@pengutronix.de>
to merge with the rest of the series.
regards
Philipp
> ---
> .../bindings/reset/amlogic,meson-reset.txt | 19 ----------
> .../bindings/reset/amlogic,meson-reset.yaml | 37 +++++++++++++++++++
> 2 files changed, 37 insertions(+), 19 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/reset/amlogic,meson-reset.txt
> create mode 100644 Documentation/devicetree/bindings/reset/amlogic,meson-reset.yaml
>
> diff --git a/Documentation/devicetree/bindings/reset/amlogic,meson-reset.txt b/Documentation/devicetree/bindings/reset/amlogic,meson-reset.txt
> deleted file mode 100644
> index 28ef6c295c76..000000000000
> --- a/Documentation/devicetree/bindings/reset/amlogic,meson-reset.txt
> +++ /dev/null
> @@ -1,19 +0,0 @@
> -Amlogic Meson SoC Reset Controller
> -=======================================
> -
> -Please also refer to reset.txt in this directory for common reset
> -controller binding usage.
> -
> -Required properties:
> -- compatible: Should be "amlogic,meson8b-reset", "amlogic,meson-gxbb-reset" or
> - "amlogic,meson-axg-reset".
> -- reg: should contain the register address base
> -- #reset-cells: 1, see below
> -
> -example:
> -
> -reset: reset-controller {
> - compatible = "amlogic,meson-gxbb-reset";
> - reg = <0x0 0x04404 0x0 0x20>;
> - #reset-cells = <1>;
> -};
> diff --git a/Documentation/devicetree/bindings/reset/amlogic,meson-reset.yaml b/Documentation/devicetree/bindings/reset/amlogic,meson-reset.yaml
> new file mode 100644
> index 000000000000..00917d868d58
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/reset/amlogic,meson-reset.yaml
> @@ -0,0 +1,37 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +# Copyright 2019 BayLibre, SAS
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/reset/amlogic,meson-reset.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Amlogic Meson SoC Reset Controller
> +
> +maintainers:
> + - Neil Armstrong <narmstrong@baylibre.com>
> +
> +properties:
> + compatible:
> + enum:
> + - amlogic,meson8b-reset # Reset Controller on Meson8b and compatible SoCs
> + - amlogic,meson-gxbb-reset # Reset Controller on GXBB and compatible SoCs
> + - amlogic,meson-axg-reset # Reset Controller on AXG and compatible SoCs
> +
> + reg:
> + maxItems: 1
> +
> + "#reset-cells":
> + const: 1
> +
> +required:
> + - compatible
> + - reg
> + - "#reset-cells"
> +
> +examples:
> + - |
> + reset-controller@c884404 {
> + compatible = "amlogic,meson-gxbb-reset";
> + reg = <0xc884404 0x20>;
> + #reset-cells = <1>;
> + };
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-08-06 7:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 12:03 [RFCv2 0/9] dt-bindings: first tentative of conversion to yaml format Neil Armstrong
2019-08-05 12:03 ` [RFCv2 1/9] dt-bindings: mailbox: meson-mhu: convert to yaml Neil Armstrong
2019-08-07 14:34 ` Maxime Ripard
2019-08-05 12:03 ` [RFCv2 2/9] dt-bindings: rng: amlogic,meson-rng: " Neil Armstrong
2019-08-06 19:19 ` Martin Blumenstingl
2019-08-05 12:03 ` [RFCv2 3/9] dt-bindings: spi: meson: " Neil Armstrong
2019-08-05 21:45 ` Rob Herring
2019-08-05 12:03 ` [RFCv2 4/9] dt-bindings: reset: amlogic,meson-reset: " Neil Armstrong
2019-08-06 7:41 ` Philipp Zabel [this message]
2019-08-06 19:12 ` [RFCv2 4/9] dt-bindings: reset: amlogic, meson-reset: " Martin Blumenstingl
2019-08-05 12:03 ` [RFCv2 5/9] dt-bindings: arm: amlogic: amlogic, meson-gx-ao-secure: " Neil Armstrong
2019-08-05 12:03 ` [RFCv2 6/9] dt-bindings: phy: meson-g12a-usb2-phy: " Neil Armstrong
2019-08-06 19:21 ` Martin Blumenstingl
2019-08-05 12:03 ` [RFCv2 7/9] dt-bindings: phy: meson-g12a-usb3-pcie-phy: " Neil Armstrong
2019-08-05 12:03 ` [RFCv2 8/9] dt-bindings: serial: meson-uart: " Neil Armstrong
2019-08-06 19:18 ` Martin Blumenstingl
2019-08-05 12:03 ` [RFCv2 9/9] dt-bindings: watchdog: meson-gxbb-wdt: " Neil Armstrong
2019-08-07 17:59 ` Guenter Roeck
2019-08-05 21:51 ` [RFCv2 0/9] dt-bindings: first tentative of conversion to yaml format Rob Herring
2019-08-06 7:42 ` Neil Armstrong
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=1565077264.4951.4.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.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).