From: Rob Herring <robh@kernel.org>
To: Romain Perier <romain.perier@gmail.com>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Daniel Palmer <daniel@0x0f.com>,
Mohammed Billoo <mohammed.billoo@gmail.com>,
linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] Documentation: watchdog: Add Mstar MSC313e WDT devicetree bindings documentation
Date: Fri, 4 Jun 2021 16:30:28 -0500 [thread overview]
Message-ID: <20210604213028.GA3941849@robh.at.kernel.org> (raw)
In-Reply-To: <20210530072645.10379-2-romain.perier@gmail.com>
On Sun, May 30, 2021 at 09:26:43AM +0200, Romain Perier wrote:
> This adds the documentation for the devicetree bindings of the Mstar
> MSC313e watchdog driver, found from MSC313e SoCs and newer.
'dt-bindings: watchdog: ...' for the subject.
>
> Signed-off-by: Romain Perier <romain.perier@gmail.com>
> ---
> .../bindings/watchdog/msc313e-wdt.yaml | 40 +++++++++++++++++++
mstar,msc313e-wdt.yaml
> 1 file changed, 40 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/msc313e-wdt.yaml
>
> diff --git a/Documentation/devicetree/bindings/watchdog/msc313e-wdt.yaml b/Documentation/devicetree/bindings/watchdog/msc313e-wdt.yaml
> new file mode 100644
> index 000000000000..70b8e1be5e8e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/watchdog/msc313e-wdt.yaml
> @@ -0,0 +1,40 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/watchdog/msc313e-wdt.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MStar Watchdog Device Tree Bindings
> +
> +maintainers:
> + - Daniel Palmer <daniel@0x0f.com>
> + - Romain Perier <romain.perier@gmail.com>
> +
> +allOf:
> + - $ref: watchdog.yaml#
> +
> +properties:
> + compatible:
> + enum:
> + - mstar,msc313e-wdt
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - clocks
> + - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + watchdog: watchdog@6000 {
Drop unused labels.
> + compatible = "mstar,msc313e-wdt";
> + reg = <0x6000 0x1f>;
> + clocks = <&xtal_div2>;
> + };
> --
> 2.30.2
next prev parent reply other threads:[~2021-06-04 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 7:26 [PATCH v2 0/3] Add watchdog for Mstar SoCs Romain Perier
2021-05-30 7:26 ` [PATCH v2 1/3] Documentation: watchdog: Add Mstar MSC313e WDT devicetree bindings documentation Romain Perier
2021-06-04 21:30 ` Rob Herring [this message]
2021-06-05 16:54 ` Romain Perier
2021-05-30 7:26 ` [PATCH v2 2/3] watchdog: Add Mstar MSC313e WDT driver Romain Perier
2021-05-30 7:26 ` [PATCH v2 3/3] ARM: dts: mstar: Add watchdog device_node definition Romain Perier
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=20210604213028.GA3941849@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mohammed.billoo@gmail.com \
--cc=romain.perier@gmail.com \
--cc=wim@linux-watchdog.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).