From: Crystal Guo <crystal.guo@mediatek.com>
To: <linux@roeck-us.net>, <robh+dt@kernel.org>, <matthias.bgg@gmail.com>
Cc: <srv_heupstream@mediatek.com>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-watchdog@vger.kernel.org>,
<seiya.wang@mediatek.com>, <erin.lo@mediatek.com>,
Crystal Guo <crystal.guo@mediatek.com>
Subject: [v3,3/3] watchdog: mtk_wdt: merge all the reset numbers in one head file
Date: Wed, 29 Jul 2020 14:30:49 +0800 [thread overview]
Message-ID: <1596004249-28655-4-git-send-email-crystal.guo@mediatek.com> (raw)
In-Reply-To: <1596004249-28655-1-git-send-email-crystal.guo@mediatek.com>
mt8xxx-resets.h actually just used to define TOPRGU_SW_RST_NUM.
Instead of resubmit a new mt8xxx-reset.h for a new IC, merge all
the reset numbers in one head file.
Signed-off-by: Crystal Guo <crystal.guo@mediatek.com>
---
drivers/watchdog/mtk_wdt.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/watchdog/mtk_wdt.c b/drivers/watchdog/mtk_wdt.c
index d6a6393..5000a49 100644
--- a/drivers/watchdog/mtk_wdt.c
+++ b/drivers/watchdog/mtk_wdt.c
@@ -9,8 +9,7 @@
* Based on sunxi_wdt.c
*/
-#include <dt-bindings/reset-controller/mt2712-resets.h>
-#include <dt-bindings/reset-controller/mt8183-resets.h>
+#include <dt-bindings/reset-controller/mtk-resets.h>
#include <linux/delay.h>
#include <linux/err.h>
#include <linux/init.h>
--
1.8.1.1.dirty
prev parent reply other threads:[~2020-07-29 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 6:30 [v2,0/3] mtk_wdt: merge all the reset numbers in one head file Crystal Guo
2020-07-29 6:30 ` [v2,1/3] dt-bindings: watchdog: modify description for mt2712 and mt8183 Crystal Guo
2020-07-29 6:30 ` [v2,2/3] dt-bindings: watchdog: add a new head file for toprgu reset-controllers Crystal Guo
2020-07-29 7:42 ` Matthias Brugger
2020-07-29 8:11 ` Crystal Guo
2020-07-29 8:15 ` Matthias Brugger
2020-07-29 8:35 ` Crystal Guo
2020-07-29 6:30 ` Crystal Guo [this message]
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=1596004249-28655-4-git-send-email-crystal.guo@mediatek.com \
--to=crystal.guo@mediatek.com \
--cc=erin.lo@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=seiya.wang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
/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;
as well as URLs for NNTP newsgroup(s).