linux-kernel - [PATCH v2 0/8] watchdog: w83627hf: Convert to watchdog infrastructure

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: <1362957300-18223-1-git-send-email-linux@roeck-us.net>
Date:	Sun, 10 Mar 2013 16:14:53 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	linux-watchdog@...r.kernel.org
Cc:	Wim Van Sebroeck <wim@...ana.be>, linux-kernel@...r.kernel.org,
	Guenter Roeck <linux@...ck-us.net>
Subject: [PATCH v2 0/8] watchdog: w83627hf: Convert to watchdog infrastructure

Convert to watchdog infrastructure, cleanup, add support for additional
chips, and merge with W83697HF and W83697UG watchdog drivers.

Tested with W83627UHG, NCT6775, NCT6776. Additional test feedback
for other chips would be appreciated.

Original idea was to prepare the driver for use as a client to an MFD driver,
but I found that requesting memory with request_muxed_region works just as well
and has less impact. v2 includes the knowledge gained from converting the
driver to an MFD client driver, but without the actual conversion.

v2: Tested with W83627UHG
    Retain timeout module parameter; use watchdog_init_timeout to set it
    Eliminate some cosmetic changes
    Drop spinlock.h include
    Keep "initialized" message
    Don't try to configure WDTO for W83627UHG and W83627EHF
    Don't report the nowayout option with the 'initializing' message
    Use request_muxed_region to reserve memory range only while needed
    Add support for W83627S, W83627DHG-P, W83667HG, and NCT6779
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/