linux-kernel - Re: [External] Re: [PATCH v2] watchdog: add in watchdog for nct6686

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-prev] [day] [month] [year] [list]

Date: Sat, 24 Feb 2024 09:25:54 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: David Ober <dober@...ovo.com>
Cc: Mark Pearson <mpearson-lenovo@...ebb.ca>,
	David Ober <dober6023@...il.com>,
	"wim@...ux-watchdog.org" <wim@...ux-watchdog.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-watchdog@...r.kernel.org" <linux-watchdog@...r.kernel.org>
Subject: Re: [External] Re: [PATCH v2] watchdog: add in watchdog for nct6686

On Sat, Feb 24, 2024 at 05:00:04PM +0000, David Ober wrote:
> Hi
> 
>    I understand the issue of the first come first grab but when I attempted to add this to the hwmon you insisted that that was not the correct place and to create a watchdog module so if both can not be loaded then would it have not been better to add it to the hwmon like some of the other chips.
> 

Two options:

- Add it to the hwmon driver. Not a preferred solution.
- Implement a mfd driver which controls access to the chip
  (preferrably through regmap) and instantiates both the hwmon
  driver and the watchdog driver.

Guenter