[PATCH v4 0/3] watchdog: w83627hf_wdt: various improvements

Paul Louvel <[email protected]> Tue, 07 Jul 2026 17:45:00 +0200
Newsgroups org.kernel.vger.linux-watchdog,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
This series improves the w83627hf_wdt driver with three enhancements.

- Patch 1 distinguishes NCT6126 from NCT6116 by reading the low byte of
  the chip ID.

- Patch 2 replaces the hardcoded "W83627HF Watchdog" identity string
  with the actual probed chip name.

- Patch 3 also sets WDOG_HW_RUNNING instead of a single keepalive when
  the watchdog is already running at boot.

Signed-off-by: Paul Louvel <[email protected]>
---
Changes in v4:
- Updated cover letter.
- The first patch does not add support to NCT6126, but rather correctly
  identify it. Changed the commit message that was misleading.
- The second patch in v3 brings unexpected behavior if
  WATCHDOG_HANDLE_BOOT_ENABLED is disabled. Instead, keep the manual
  refresh, and also set the WDOG_HW_RUNNING bit.
- Add another patch to correctly identify the probed chip via
  WDIOC_GETSUPPORT.
- Link to v3: https://patch.msgid.link/[email protected]

Changes in v3:
- Forgot to add case in w83627hf_init() with the chip. Not detected
  during testing because the BIOS probably configure it anyway on boot.
- Link to v2: https://patch.msgid.link/[email protected]

Changes in v2:
- Small mistake in the first patch. The NCT6116_ID macro is redefined.
  Fix it.

To: Wim Van Sebroeck <[email protected]>
To: Guenter Roeck <[email protected]>
Cc: [email protected]
Cc: [email protected]

---
Paul Louvel (3):
      watchdog: w83627hf_wdt: Correctly identify Nuvoton NCT6126 chip
      watchdog: w83627hf_wdt: Report the probed chip name via WDIOC_GETSUPPORT
      watchdog: w83627hf_wdt: Use WDOG_HW_RUNNING for running chip on boot

 drivers/watchdog/w83627hf_wdt.c | 22 +++++++++++++++++-----
 1 file changed, 17 insertions(+), 5 deletions(-)
---
base-commit: 028ef9c96e96197026887c0f092424679298aae8
change-id: 20260705-w83627hf_wdt-nct6126d-9a016bf7c936

Best regards,
--  
Paul Louvel, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com