From: Tzung-Bi Shih <tzungbi@google.com>
To: Christine Zhu <christine.zhu@mediatek.com>
Cc: linux@roeck-us.net, robh+dt@kernel.org, wim@linux-watchdog.org,
matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
seiya.wang@mediatek.com, linux-watchdog@vger.kernel.org,
rex-bc.chen@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com,
srv_heupstream@mediatek.com
Subject: Re: [v1,3/3] watchdog: mt8195: add wdt support
Date: Mon, 21 Jun 2021 14:11:23 +0800 [thread overview]
Message-ID: <CA+Px+wXG=KDRKzm-bS95tnmpbBTCD3C72nhi3RJGw6PG6Cj-hQ@mail.gmail.com> (raw)
In-Reply-To: <20210620134954.15233-4-Christine.Zhu@mediatek.com>
On Sun, Jun 20, 2021 at 9:50 PM Christine Zhu
<Christine.Zhu@mediatek.com> wrote:
> add support for watchdog device found in MT8195 SoC
Please write complete sentences. For example, "Supports MT8195
watchdog device."
> Change-Id: Ib2434cf2d47a2e14916056f08a4fc630569624ed
Remove the unneeded tag.
> +static const struct mtk_wdt_data mt8195_data = {
> + .toprgu_sw_rst_num = MT8195_TOPRGU_SW_RST_NUM,
> +};
Expect to see the of_device_id (i.e. mtk_wdt_dt_ids) has the newly
introduced compatible string and use the mt8195_data but failed to
find it.
next prev parent reply other threads:[~2021-06-21 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 13:49 [v1,0/3] watchdog: mt8195: add wdt support Christine Zhu
[not found] ` <20210620134954.15233-4-Christine.Zhu@mediatek.com>
2021-06-21 6:11 ` Tzung-Bi Shih [this message]
2021-06-21 6:11 ` Tzung-Bi Shih
[not found] ` <20210620134954.15233-2-Christine.Zhu@mediatek.com>
2021-06-21 6:11 ` [v1,1/3] dt-binding: mt8195: update mtk-wdt document Tzung-Bi Shih
[not found] ` <20210620134954.15233-3-Christine.Zhu@mediatek.com>
2021-06-21 6:11 ` [v1,2/3] dt-binding: mt8195: add toprgu reset-controller head file Tzung-Bi Shih
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='CA+Px+wXG=KDRKzm-bS95tnmpbBTCD3C72nhi3RJGw6PG6Cj-hQ@mail.gmail.com' \
--to=tzungbi@google.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=christine.zhu@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=rex-bc.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=seiya.wang@mediatek.com \
--cc=srv_heupstream@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).