From: Matt Fleming <matt@codeblueprint.co.uk>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jean Delvare <jdelvare@suse.com>,
Wolfram Sang <wsa@the-dreams.de>,
Matt Fleming <matt.fleming@intel.com>
Subject: [PATCH v2 0/3] iTCO_wdt: Add support for Intel Sunrisepoint
Date: Wed, 29 Jul 2015 13:10:41 +0100 [thread overview]
Message-ID: <1438171844-24861-1-git-send-email-matt@codeblueprint.co.uk> (raw)
From: Matt Fleming <matt.fleming@intel.com>
Starting with Intel Sunrisepoint (Skylake PCH) the TCO watchdog device
is now on the SMBUS, whereas for previous ICH/PCH it was on the LPC bus.
Because iTCO_wdt devices may now appear on either the LPC bus or the
SMBUS we need to abstract the bus information into an agnostic structure
instead of the existing 'lpc_ich_info' which tightly integrates both the
lpc_ich and iTCO_wdt drivers.
The first patch introduces a platform data structure to handle this and
shuffles the existing code around. The other patches add the
device-specific information to the i2c-i801 and iTCO_wdt drivers.
Patches based against v4.2-rc4, if there's some other tree I should base
this on, please let me know.
Comments welcome!
Changes in v2:
- Use lowercase for all new files and data structures
- Allocate platform data with devm_kzalloc()
- Move Kconfig changes to final patch and use 'select', not 'depends'
- Swap strcpy() for strlcpy()
- Fixup use of lpc_ich_info in intel_pmc_ipc which was missed in v1
- Don't use bitops in i2c-i801
- Remove superfluous NULL checks in i2c-i801
- Explicitly list reboot bit versions in no_reboot_bit()
- Use switch/case construst instead of crazy if else
- Fold original fixups from PATCH 4 and 5 into PATCH 1 and 2
Matt Fleming (2):
iTCO_wdt: Expose watchdog properties using platform data
iTCO_wdt: Add support for TCO on Intel Sunrisepoint
Mika Westerberg (1):
i2c: i801: Create iTCO device on newer Intel PCHs
drivers/i2c/busses/i2c-i801.c | 120 ++++++++++++++++++++++++++++++++-
drivers/mfd/lpc_ich.c | 32 ++++++++-
drivers/platform/x86/intel_pmc_ipc.c | 9 ++-
drivers/watchdog/Kconfig | 3 +-
drivers/watchdog/iTCO_wdt.c | 77 ++++++++++++---------
include/linux/mfd/lpc_ich.h | 6 --
include/linux/platform_data/itco_wdt.h | 19 ++++++
7 files changed, 219 insertions(+), 47 deletions(-)
create mode 100644 include/linux/platform_data/itco_wdt.h
--
2.1.0
next reply other threads:[~2015-07-29 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 12:10 Matt Fleming [this message]
2015-07-29 12:10 ` [PATCH v2 1/3] iTCO_wdt: Expose watchdog properties using platform data Matt Fleming
2015-07-29 15:35 ` Lee Jones
2015-07-29 16:39 ` Matt Fleming
2015-07-30 8:53 ` Lee Jones
2015-07-30 9:14 ` Matt Fleming
2015-07-30 11:08 ` Lee Jones
2015-07-29 12:10 ` [PATCH v2 2/3] i2c: i801: Create iTCO device on newer Intel PCHs Matt Fleming
2015-07-29 17:06 ` Guenter Roeck
2015-07-29 12:10 ` [PATCH v2 3/3] iTCO_wdt: Add support for TCO on Intel Sunrisepoint Matt Fleming
2015-07-29 17:06 ` 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=1438171844-24861-1-git-send-email-matt@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=wim@iguana.be \
--cc=wsa@the-dreams.de \
/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