From: Rob Herring <robh@kernel.org>
To: Bharat Bhushan <bbhushan2@marvell.com>
Cc: wim@linux-watchdog.org, linux@roeck-us.net,
krzysztof.kozlowski+dt@linaro.org,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: watchdog: marvell octeonTX2 GTI watchdog driver
Date: Fri, 24 Mar 2023 15:34:37 -0500 [thread overview]
Message-ID: <20230324203437.GA2439497-robh@kernel.org> (raw)
In-Reply-To: <20230324145652.19221-1-bbhushan2@marvell.com>
On Fri, Mar 24, 2023 at 08:26:51PM +0530, Bharat Bhushan wrote:
> Add binding documentation for the Marvell octeonTX2
> GTI watchdog driver.
>
> Signed-off-by: Bharat Bhushan <bbhushan2@marvell.com>
> ---
> .../watchdog/marvel-octeontx2-wdt.yaml | 43 +++++++++++++++++++
The comics?
Use compatible string for filename.
> 1 file changed, 43 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/marvel-octeontx2-wdt.yaml
>
> diff --git a/Documentation/devicetree/bindings/watchdog/marvel-octeontx2-wdt.yaml b/Documentation/devicetree/bindings/watchdog/marvel-octeontx2-wdt.yaml
> new file mode 100644
> index 000000000000..586b3c1bd780
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/watchdog/marvel-octeontx2-wdt.yaml
> @@ -0,0 +1,43 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/watchdog/marvel-octeontx2-wdt.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Marvell OcteonTX2 GTI watchdog
> +
> +allOf:
> + - $ref: "watchdog.yaml#"
Drop quotes
> +
> +maintainers:
> + - Bharat Bhushan <bbhushan2@marvell.com>
> +
> +properties:
> + compatible:
> + enum:
> + - mrvl,octeontx2-gti-wdt
'mrvl' is deprecated. Use 'marvell'
> +
> + reg:
> + maxItems: 2
Need to define what each entry is.
> +
> + interrupts:
> + minItems: 1
> + maxItems: 36
Need to define what each entry is. How does the h/w have a variable
number of interrupts?
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + watch-dog@802000040000 {
watchdog@...
> + compatible = "mrvl,octeontx2-gti-wdt";
> + reg = <0x8020 0x40000 0x0 0x20000>;
> + interrupts = <0 38 1>, /* Core-0 */
> + <0 39 1>; /* Core-1 */
> + };
> +
> +...
> --
> 2.17.1
>
next prev parent reply other threads:[~2023-03-24 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 14:56 [PATCH 1/2] dt-bindings: watchdog: marvell octeonTX2 GTI watchdog driver Bharat Bhushan
2023-03-24 14:56 ` [PATCH 2/2] Watchdog: octeontx2: Add Pseudo-NMI " Bharat Bhushan
2023-03-24 21:04 ` Thomas Weißschuh
2023-04-13 10:20 ` [EXT] " Bharat Bhushan
2023-03-24 22:03 ` Guenter Roeck
2023-04-13 10:22 ` [EXT] " Bharat Bhushan
2023-03-26 8:40 ` kernel test robot
2023-03-24 20:17 ` [PATCH 1/2] dt-bindings: watchdog: marvell octeonTX2 " Rob Herring
2023-03-24 20:34 ` Rob Herring [this message]
2023-04-13 10:14 ` [EXT] " Bharat Bhushan
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=20230324203437.GA2439497-robh@kernel.org \
--to=robh@kernel.org \
--cc=bbhushan2@marvell.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).