From: Rex-BC Chen <rex-bc.chen@mediatek.com>
To: <wim@linux-watchdog.org>, <linux@roeck-us.net>,
<matthias.bgg@gmail.com>, <robh+dt@kernel.org>,
<p.zabel@pengutronix.de>
Cc: <runyang.chen@mediatek.com>, <linux-watchdog@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Rex-BC Chen <rex-bc.chen@mediatek.com>
Subject: [RESEND V2 0/3] Add watchdog support for MT8186 SoC
Date: Tue, 1 Mar 2022 13:44:02 +0800 [thread overview]
Message-ID: <20220301054405.25021-1-rex-bc.chen@mediatek.com> (raw)
resend v2:
1. Fix topic to V2.
v2:
1. Squash [1] into [2] in v1.
2. Add tags of acked-by and reviewed-by.
[1]: [3/4] dt-bindings: reset: mt8186: add DSI reset bit for MMSYS
[2]: [2/4] dt-bindings: reset: mt8186: add toprgu reset-controller header file
v1:
1. Add mt8186-resets.h to define definition of reset bits.
2. Add wdt compatible for MT8186.
Rex-BC Chen (1):
dt-bindings: watchdog: Add compatible for MediaTek MT8186
Runyang Chen (2):
dt-bindings: reset: mt8186: add reset-controller header file
watchdog: mediatek: mt8186: add wdt support
.../devicetree/bindings/watchdog/mtk-wdt.txt | 1 +
drivers/watchdog/mtk_wdt.c | 6 ++++
include/dt-bindings/reset/mt8186-resets.h | 36 +++++++++++++++++++
3 files changed, 43 insertions(+)
create mode 100644 include/dt-bindings/reset/mt8186-resets.h
--
2.18.0
next reply other threads:[~2022-03-01 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 5:44 Rex-BC Chen [this message]
2022-03-01 5:44 ` [RESEND V2 1/3] dt-bindings: watchdog: Add compatible for MediaTek MT8186 Rex-BC Chen
2022-03-01 5:44 ` [RESEND V2 2/3] dt-bindings: reset: mt8186: add reset-controller header file Rex-BC Chen
2022-03-01 5:44 ` [RESEND V2 3/3] watchdog: mediatek: mt8186: add wdt support Rex-BC Chen
2022-03-10 8:34 ` [RESEND V2 0/3] Add watchdog support for MT8186 SoC Rex-BC Chen
2022-03-10 9:15 ` Rex-BC Chen
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=20220301054405.25021-1-rex-bc.chen@mediatek.com \
--to=rex-bc.chen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--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=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=runyang.chen@mediatek.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;
as well as URLs for NNTP newsgroup(s).