From: Yu Chien Peter Lin <peterlin@andestech.com>
To: opensbi@lists.infradead.org
Subject: [PATCH 3/4] docs: andes-ae350.md: fix watchdog nodename in dts example
Date: Mon, 28 Nov 2022 16:30:45 +0800 [thread overview]
Message-ID: <20221128083046.6799-4-peterlin@andestech.com> (raw)
In-Reply-To: <20221128083046.6799-1-peterlin@andestech.com>
The example should use watchdog as nodename instead of wdt.
This is defined in watchdog common schemas:
https://github.com/torvalds/linux/blob/v6.0/Documentation/devicetree/bindings/watchdog/watchdog.yaml#L19
Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
---
docs/platform/andes-ae350.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/platform/andes-ae350.md b/docs/platform/andes-ae350.md
index 4739951..8fc8ec6 100644
--- a/docs/platform/andes-ae350.md
+++ b/docs/platform/andes-ae350.md
@@ -178,7 +178,7 @@ DTS Example: (Quad-core AX45MP)
&CPU3_intc 7 >;
};
- wdt: wdt at f0500000 {
+ wdt: watchdog at f0500000 {
compatible = "andestech,atcwdt200";
reg = <0x00000000 0xf0500000 0x00000000 0x00001000>;
interrupts = <3 4>;
--
2.34.1
next prev parent reply other threads:[~2022-11-28 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 8:30 [PATCH 0/4] Enable generic platform support for AE350 Yu Chien Peter Lin
2022-11-28 8:30 ` [PATCH 1/4] platform: generic/andes: " Yu Chien Peter Lin
2022-11-28 10:34 ` Lad, Prabhakar
2022-11-28 20:28 ` Yu-Chien Peter Lin
2022-11-30 12:40 ` Lad, Prabhakar
2022-12-02 16:10 ` Bin Meng
2022-11-28 8:30 ` [PATCH 2/4] docs: platform: Update AE350 and generic platform documentation Yu Chien Peter Lin
2022-12-02 16:10 ` Bin Meng
2022-12-05 9:38 ` Yu-Chien Peter Lin
2022-11-28 8:30 ` Yu Chien Peter Lin [this message]
2022-12-02 16:10 ` [PATCH 3/4] docs: andes-ae350.md: fix watchdog nodename in dts example Bin Meng
2022-11-28 8:30 ` [PATCH 4/4] scripts/create-binary-archive.sh: remove andes/ae350 build directory Yu Chien Peter Lin
2022-12-02 16:10 ` Bin Meng
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=20221128083046.6799-4-peterlin@andestech.com \
--to=peterlin@andestech.com \
--cc=opensbi@lists.infradead.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