From: Guenter Roeck <linux@roeck-us.net>
To: Roman Vivchar <rva333@protonmail.com>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Ben Grisdale <bengris32@protonmail.ch>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 2/3] watchdog: mediatek: add mt6797 support
Date: Thu, 19 Nov 2026 20:29:36 -0800 [thread overview]
Message-ID: <f0ea8f8d-eef7-4d13-8180-ea3e297c407c@roeck-us.net> (raw)
In-Reply-To: <20261110-6797-wdt-v1-2-7f07755b6074@protonmail.com>
On Tue, Nov 10, 2026 at 09:22:22PM +0200, Roman Vivchar wrote:
> From: Roman Vivchar <rva333@protonmail.com>
>
> Add support for mt6797 SoC watchdog, which provides 17 software resets.
> The mapping table uses bits from the datasheet [1].
>
> Link: https://www.96boards.org/documentation/consumer/mediatekx20/additional-docs/docs/MT6797_Register_Table_Part_1.pdf [1]
> Signed-off-by: Roman Vivchar <rva333@protonmail.com>
Applied.
Thanks,
Guenter
next prev parent reply other threads:[~2026-11-20 4:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 19:22 [PATCH 0/3] watchdog: mediatek: fix mt6797 Roman Vivchar via B4 Relay
2026-11-10 19:22 ` [PATCH 1/3] dt-bindings: watchdog: mediatek,mtk-wdt: fix mt6797 compatible Roman Vivchar via B4 Relay
2026-11-19 23:17 ` Rob Herring (Arm)
2026-11-20 4:28 ` Guenter Roeck
2026-11-10 19:22 ` [PATCH 2/3] watchdog: mediatek: add mt6797 support Roman Vivchar via B4 Relay
2026-11-20 4:29 ` Guenter Roeck [this message]
2026-11-10 19:22 ` [PATCH 3/3] arm64: dts: mediatek: mt6797: fix wdt compatible and add reset-cells Roman Vivchar via B4 Relay
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=f0ea8f8d-eef7-4d13-8180-ea3e297c407c@roeck-us.net \
--to=linux@roeck-us.net \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bengris32@protonmail.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@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=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=rva333@protonmail.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®