From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-mips@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Ethan Nelson-Moore <enelsonmoore@gmail.com>,
Eric Biggers <ebiggers@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mingyu Wang <25181214217@stu.xidian.edu.cn>,
Robert Marko <robert.marko@sartura.hr>,
linux-watchdog@vger.kernel.org (open list:WATCHDOG DEVICE
DRIVERS),
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list),
manuel.lauss@gmail.com
Subject: [PATCH 0/5] MTX-1 watchdog driver removal
Date: Fri, 16 Oct 2026 15:16:12 -0700 [thread overview]
Message-ID: <20261016221617.2223004-1-f.fainelli@gmail.com> (raw)
This patch series removes the bespoke mtx-1_wdt driver and migrates it
to the generic gpio_wdt driver which it should have done ever since
gpio_wdt existed.
Assuming the patches are satisfactory, I suppose it would be easier to
merge those via the watchdog tree than the MIPS tree?
Florian Fainelli (5):
watchdog: gpio: Allow devices described by software nodes
dt-bindings: watchdog: gpio: Describe minimum heartbeat intervals
watchdog: gpio: Support watchdogs with a minimum heartbeat interval
MIPS: Alchemy: Use the GPIO watchdog driver on MTX-1
watchdog: Remove the MTX-1 watchdog driver
.../bindings/watchdog/linux,wdt-gpio.yaml | 11 +-
arch/mips/alchemy/board-mtx1.c | 8 +-
arch/mips/configs/mtx1_defconfig | 2 +-
drivers/watchdog/Kconfig | 9 +-
drivers/watchdog/Makefile | 1 -
drivers/watchdog/gpio_wdt.c | 15 +-
drivers/watchdog/mtx-1_wdt.c | 245 ------------------
7 files changed, 31 insertions(+), 260 deletions(-)
delete mode 100644 drivers/watchdog/mtx-1_wdt.c
--
2.53.0
next reply other threads:[~2026-10-16 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 22:16 Florian Fainelli [this message]
2026-10-16 22:16 ` [PATCH 1/5] watchdog: gpio: Allow devices described by software nodes Florian Fainelli
2026-10-16 22:16 ` [PATCH 2/5] dt-bindings: watchdog: gpio: Describe minimum heartbeat intervals Florian Fainelli
2026-10-16 22:16 ` [PATCH 3/5] watchdog: gpio: Support watchdogs with a minimum heartbeat interval Florian Fainelli
2026-10-16 22:16 ` [PATCH 4/5] MIPS: Alchemy: Use the GPIO watchdog driver on MTX-1 Florian Fainelli
2026-10-16 22:16 ` [PATCH 5/5] watchdog: Remove the MTX-1 watchdog driver Florian Fainelli
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=20261016221617.2223004-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=25181214217@stu.xidian.edu.cn \
--cc=andrew@lunn.ch \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ebiggers@kernel.org \
--cc=enelsonmoore@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=manuel.lauss@gmail.com \
--cc=robert.marko@sartura.hr \
--cc=robh@kernel.org \
--cc=tsbogend@alpha.franken.de \
--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