From: Guenter Roeck <linux@roeck-us.net>
To: linux-watchdog@vger.kernel.org
Cc: Wim Van Sebroeck <wim@iguana.be>,
linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH v3 0/8] watchdog: w83627hf: Convert to watchdog infrastructure
Date: Sat, 17 Aug 2013 13:58:38 -0700 [thread overview]
Message-ID: <1376773126-2717-1-git-send-email-linux@roeck-us.net> (raw)
Convert to watchdog infrastructure, cleanup, add support for additional
chips, and merge with W83697HF and W83697UG watchdog drivers.
Tested with W83627UHG, NCT6775, NCT6776.
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.
With this set of patches, the watchdog driver for the supported chips
can be used together with the hwmon driver for those chips.
Wim, please consider merging this set of patches into 3.12. I need
both watchdog and hwmon driver running, which means I have to run
patched kernels which gets a bit annoying over time. If you don't
like the idea of merging the drivers for W83697HF and W83697UG
into this one, please drop patch 6 and 7 from the series.
v3: Reset watchdog trigger on startup
Rebased to v3.11-rc5
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
next reply other threads:[~2013-08-17 20:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 20:58 Guenter Roeck [this message]
2013-08-17 20:58 ` [PATCH v3 1/8] watchdog: w83627hf: Convert to watchdog infrastructure Guenter Roeck
2013-10-28 21:57 ` Wim Van Sebroeck
2013-10-28 23:10 ` Guenter Roeck
2013-10-29 2:43 ` [PATCH v4] " Guenter Roeck
2013-10-29 6:34 ` Wim Van Sebroeck
2013-11-17 19:12 ` Wim Van Sebroeck
2013-11-17 21:21 ` Guenter Roeck
2013-08-17 20:58 ` [PATCH v3 2/8] watchdog: w83627hf: Enable watchdog only once Guenter Roeck
2013-08-17 20:58 ` [PATCH v3 3/8] watchdog: w83627hf: Enable watchdog device only if not already enabled Guenter Roeck
2013-08-17 20:58 ` [PATCH v3 4/8] watchdog: w83627hf: Use helper functions to access superio registers Guenter Roeck
2013-08-17 20:58 ` [PATCH v3 5/8] watchdog: w83627hf: Auto-detect IO address and supported chips Guenter Roeck
2013-08-17 20:58 ` [PATCH v3 6/8] watchdog: w83627hf: Add support for W83697HF and W83697UG Guenter Roeck
2013-08-17 20:58 ` [PATCH v3 7/8] watchdog: Remove drivers " Guenter Roeck
2013-08-17 20:58 ` [PATCH v3 8/8] watchdog: w83627hf_wdt: Reset watchdog trigger during initialization Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1376773126-2717-1-git-send-email-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).