From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shresth Prasad <shresthprasad7@gmail.com>,
wim@linux-watchdog.org, linux@roeck-us.net, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
javier.carrasco.cruz@gmail.com
Subject: Re: [PATCH] dt-bindings: watchdog: img,pdc-wdt: Convert to dtschema
Date: Mon, 27 May 2024 20:47:34 +0200 [thread overview]
Message-ID: <771db1ec-115f-4b96-916f-3975ca302f55@kernel.org> (raw)
In-Reply-To: <20240527062102.3816-2-shresthprasad7@gmail.com>
On 27/05/2024 08:21, Shresth Prasad wrote:
> Convert txt bindings of ImgTec's PDC watchdog timer to dtschema to allow
> for validation.
>
> Signed-off-by: Shresth Prasad <shresthprasad7@gmail.com>
> ---
> The binding has been checked and tested against `img/pistachio_marduk.dts`
> with no errors or warnings.
> ---
Thank you for your patch. There is something to discuss/improve.
> +
> +maintainers:
> + - Shresth Prasad <shresthprasad7@gmail.com>
> +
> +
Just one blank line.
> +allOf:
> + - $ref: watchdog.yaml#
> +
> +properties:
> + compatible:
> + enum:
> + - img,pdc-wdt
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 2
Instead of maxItems please list items with description so the items will
be described.
> +
> + clock-names:
> + items:
> + - const: wdt
> + - const: sys
> +
> + interrupts:
> + description:
> + Should contain WDT interrupt
Drop description, redundant.
> + maxItems: 1
> +
> + assigned-clocks:
> + maxItems: 2
Drop property
> +
> + assigned-clock-rates:
> + maxItems: 2
Drop property
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> + - interrupts
> +
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-05-27 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 6:21 [PATCH] dt-bindings: watchdog: img,pdc-wdt: Convert to dtschema Shresth Prasad
2024-05-27 18:47 ` Krzysztof Kozlowski [this message]
2024-05-27 19:55 ` Shresth Prasad
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=771db1ec-115f-4b96-916f-3975ca302f55@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=shresthprasad7@gmail.com \
--cc=skhan@linuxfoundation.org \
--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