linux-kernel - Re: [PATCH 0/4] watchdog: MAX63xx cleanup and platform settings

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

Message-ID: <1716840274.614850.1429202273466.JavaMail.zimbra@savoirfairelinux.com>
Date:	Thu, 16 Apr 2015 12:37:53 -0400 (EDT)
From:	Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To:	linux-watchdog@...r.kernel.org
Cc:	Wim Van Sebroeck <wim@...ana.be>, linux-kernel@...r.kernel.org,
	kernel@...oirfairelinux.com, Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH 0/4] watchdog: MAX63xx cleanup and platform settings

Hi Wim, all,

> The purpose of this patchset is to add a platform data structure for the
> max63xx_wdt driver in order to setup the device in a platform code. This is
> especially handy if the driver is built-in and/or the device registers aren't
> memory mapped.
> 
> First, fix the Kconfig entry to allow building the support for architectures
> other than ARM. Then clean up the driver to help distinguish different device
> connections and to ease the introduction of new features: support for GPIO
> wired MAX63xx devices and heartbeat as a platform setting.
> 
> Tested with a GPIO wired MAX6373 on an Atom platform, with a built-in driver.
> 
> Vivien Didelot (4):
>   watchdog: MAX63XX_WATCHDOG does not depend on ARM
>   watchdog: max63xx: cleanup
>   watchdog: max63xx: add GPIO support
>   watchdog: max63xx: add heartbeat to platform data

Did you get any chance to look into merging this patchset?
(It still applies well on the latest watchdog-next/master tree.)

Best,
-v
--
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/