linux-kernel - [PATCH v3] watchdog: sunxi_wdt: Allow watchdog to remain enabled after probe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250225143638.1989755-1-regis.dargent@gmail.com>
Date: Tue, 25 Feb 2025 15:36:37 +0100
From: Regis Dargent <regis.dargent@...il.com>
To: 
Cc: Wim Van Sebroeck <wim@...ux-watchdog.org>,
	Guenter Roeck <linux@...ck-us.net>,
	Chen-Yu Tsai <wens@...e.org>,
	Jernej Skrabec <jernej.skrabec@...il.com>,
	Samuel Holland <samuel@...lland.org>,
	linux-watchdog@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	linux-sunxi@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: [PATCH v3] watchdog: sunxi_wdt: Allow watchdog to remain enabled after probe

Hi,

V3 of the patch allowing sunxi watchdog to remain enabled after probe.
This 3rd version is mainly about code cleanup.

Best regards,
Regis

Jernej Škrabec:
  I wouldn't add checks on CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED here.
  My understanding is that this config is already managed in the generic
  watchdog part, as long as the WDOG_HW_RUNNING bit matches the actual
  state of the HW watchdog timer.
  I only saw one reference in a HW driver, stm32_iwdg, where they cannot
  read the watchdog state, so they start it and set the WDOG_HW_RUNNING
  bit so that both match.