From: "Rob Herring (Arm)" <robh@kernel.org>
To: CL Wang <cl634@andestech.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
tim609@andestech.com, linux-watchdog@vger.kernel.org,
wim@linux-watchdog.org, linux@roeck-us.net
Subject: Re: [PATCH V2 1/3] dt-bindings: watchdog: Add support for Andes ATCWDT200
Date: Thu, 15 Jan 2026 14:07:12 -0600 [thread overview]
Message-ID: <176850763136.1100313.4056997529955864589.robh@kernel.org> (raw)
In-Reply-To: <20260115081444.2452357-2-cl634@andestech.com>
On Thu, 15 Jan 2026 16:14:42 +0800, CL Wang wrote:
> Add the devicetree binding documentation for the Andes ATCWDT200
> watchdog timer.
>
> ATCWDT200 is the IP name, which is embedded in AndesCore-based
> platforms or SoCs such as AE350 and Qilai.
>
> Signed-off-by: CL Wang <cl634@andestech.com>
> ---
> Changes in v2:
> - Drop redundant text "including supported properties..." from the
> commit message.
> - Clarify the relationship between ATCWDT200 IP and SoCs (AE350/Qilai)
> in the commit message.
> - Add missing type definition ($ref: uint32), enum constraint, and
> description for 'andestech,clock-source' property.
>
> ---
> .../watchdog/andestech,ae350-wdt.yaml | 53 +++++++++++++++++++
> 1 file changed, 53 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/andestech,ae350-wdt.yaml
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-01-15 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 8:14 [PATCH v2 0/3] " CL Wang
2026-01-15 8:14 ` [PATCH V2 1/3] dt-bindings: " CL Wang
2026-01-15 20:07 ` Rob Herring (Arm) [this message]
2026-01-15 8:14 ` [PATCH V2 2/3] watchdog: atcwdt200: Add driver " CL Wang
2026-05-03 21:18 ` Guenter Roeck
2026-01-15 8:14 ` [PATCH V2 3/3] MAINTAINERS: Add entry " CL Wang
2026-05-03 21:19 ` Guenter Roeck
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=176850763136.1100313.4056997529955864589.robh@kernel.org \
--to=robh@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=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
all inboxes | Powered by JetHome®