From: Krzysztof Kozlowski <krzk@kernel.org>
To: CL Wang <cl634@andestech.com>,
wim@linux-watchdog.org, linux@roeck-us.net, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org, tim609@andestech.com
Subject: Re: [PATCH 1/3] dt-bindings: watchdog: Add support for Andes ATCWDT200
Date: Wed, 7 Jan 2026 16:44:40 +0100 [thread overview]
Message-ID: <ffb1a4ef-b22c-4d59-a494-0ab703ef24d2@kernel.org> (raw)
In-Reply-To: <20260107145058.213334-2-cl634@andestech.com>
On 07/01/2026 15:50, CL Wang wrote:
> Add the devicetree binding documentation for the Andes ATCWDT200
> watchdog timer, including supported properties and usage examples.
Last part is redundant. Can you add a binding without supported
properties and without usage examples?
>
> Signed-off-by: CL Wang <cl634@andestech.com>
> ---
> .../watchdog/andestech,ae350-wdt.yaml | 48 +++++++++++++++++++
> 1 file changed, 48 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/andestech,ae350-wdt.yaml
>
> diff --git a/Documentation/devicetree/bindings/watchdog/andestech,ae350-wdt.yaml b/Documentation/devicetree/bindings/watchdog/andestech,ae350-wdt.yaml
> new file mode 100644
> index 000000000000..4726bd6734d8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/watchdog/andestech,ae350-wdt.yaml
> @@ -0,0 +1,48 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/watchdog/andestech,ae350-wdt.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Andes ATCWDT200 Watchdog Timer
> +
> +maintainers:
> + - CL Wang <cl634@andestech.com>
> +
> +allOf:
> + - $ref: watchdog.yaml#
> +
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - enum:
> + - andestech,qilai-wdt
> + - const: andestech,ae350-wdt
> + - const: andestech,ae350-wdt
Subject says WDT200, this code sais 350 and qilai. What is what? You
have entire commit msg to explain that
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + andestech,clock-source:
No clue what's this, but for sure does not pass tests without
description and type.
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - andestech,clock-source
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + watchdog@f0500000 {
> + compatible = "andestech,ae350-wdt";
> + reg = <0xf0500000 0x20>;
> + clocks = <&clk_wdt>;
> + andestech,clock-source = <0>;
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-07 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:50 [PATCH 0/3] watchdog: Add support for Andes ATCWDT200 CL Wang
2026-01-07 14:50 ` [PATCH 1/3] dt-bindings: " CL Wang
2026-01-07 15:44 ` Krzysztof Kozlowski [this message]
2026-01-09 9:35 ` CL Wang
2026-01-07 16:23 ` Rob Herring (Arm)
2026-01-12 6:59 ` CL Wang
2026-01-07 14:50 ` [PATCH 2/3] watchdog: atcwdt200: Add driver " CL Wang
2026-01-07 15:46 ` Krzysztof Kozlowski
2026-01-12 7:05 ` CL Wang
2026-01-07 14:50 ` [PATCH 3/3] MAINTAINERS: Add entry " CL Wang
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=ffb1a4ef-b22c-4d59-a494-0ab703ef24d2@kernel.org \
--to=krzk@kernel.org \
--cc=cl634@andestech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=tim609@andestech.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