From: Conor Dooley <conor@kernel.org>
To: Bharat Bhushan <bbhushan2@marvell.com>
Cc: wim@linux-watchdog.org, linux@roeck-us.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sgoutham@marvell.com
Subject: Re: [PATCH 1/2 v8] dt-bindings: watchdog: marvell GTI system watchdog driver
Date: Fri, 26 May 2023 20:37:10 +0100 [thread overview]
Message-ID: <20230526-bondless-slather-5de0a5659353@spud> (raw)
In-Reply-To: <20230526062626.1180-1-bbhushan2@marvell.com>
[-- Attachment #1: Type: text/plain, Size: 2585 bytes --]
Yo Bharat,
On Fri, May 26, 2023 at 11:56:25AM +0530, Bharat Bhushan wrote:
> Add binding documentation for the Marvell GTI system
> watchdog driver.
>
> Signed-off-by: Bharat Bhushan <bbhushan2@marvell.com>
> ---
> v8:
> - Compatible name as per soc name
I am sorry, but I do not understand this.
>
> .../watchdog/marvell,octeontx2-wdt.yaml | 73 +++++++++++++++++++
> 1 file changed, 73 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/marvell,octeontx2-wdt.yaml
>
> diff --git a/Documentation/devicetree/bindings/watchdog/marvell,octeontx2-wdt.yaml b/Documentation/devicetree/bindings/watchdog/marvell,octeontx2-wdt.yaml
> new file mode 100644
> index 000000000000..3c642359d960
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/watchdog/marvell,octeontx2-wdt.yaml
> @@ -0,0 +1,73 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/watchdog/marvell,octeontx2-wdt.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Marvell Global Timer (GTI) system watchdog
> +
> +allOf:
> + - $ref: watchdog.yaml#
From v7:
Put allOf after maintainers:.
> +
> +maintainers:
> + - Bharat Bhushan <bbhushan2@marvell.com>
> +
> +properties:
> + compatible:
> + enum:
> + - marvell,cn9670-wdt
> + - marvell,cn9880-wdt
> + - marvell,cnf9535-wdt
> + - marvell,cn10624-wdt
> + - marvell,cn10308-wdt
> + - marvell,cnf10518-wdt
static const struct of_device_id gti_wdt_of_match[] = {
{ .compatible = "marvell,cn9670-wdt", .data = &match_data_octeontx2},
{ .compatible = "marvell,cn9880-wdt", .data = &match_data_octeontx2},
{ .compatible = "marvell,cnf9535-wdt", .data = &match_data_octeontx2},
{ .compatible = "marvell,cn10624-wdt", .data = &match_data_cn10k},
{ .compatible = "marvell,cn10308-wdt", .data = &match_data_cn10k},
{ .compatible = "marvell,cnf10518-wdt", .data = &match_data_cn10k},
This is a fat hint that you should be using fallback compatibles here.
You even had a fallback setup in your last revision, but you seem to
have removed it alongside the removal of the wildcards. Why did you do
that?
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + minItems: 1
From v7:
maxItems instead. You see it is different than above properties?
> +
> + clock-names:
> + minItems: 1
From v7:
Need to define names.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-26 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 6:26 [PATCH 1/2 v8] dt-bindings: watchdog: marvell GTI system watchdog driver Bharat Bhushan
2023-05-26 6:26 ` [PATCH 2/2 v8] Watchdog: Add marvell GTI " Bharat Bhushan
2023-05-27 16:12 ` kernel test robot
2023-05-29 13:38 ` Guenter Roeck
2023-05-30 4:08 ` [EXT] " Bharat Bhushan
2023-05-26 19:37 ` Conor Dooley [this message]
2023-05-27 14:53 ` [EXT] Re: [PATCH 1/2 v8] dt-bindings: watchdog: marvell GTI system " Bharat Bhushan
2023-05-27 16:10 ` Conor Dooley
2023-05-29 6:14 ` Bharat Bhushan
2023-05-29 12:34 ` Conor Dooley
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=20230526-bondless-slather-5de0a5659353@spud \
--to=conor@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=robh+dt@kernel.org \
--cc=sgoutham@marvell.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