From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Jean Delvare <jdelvare@suse.com>,
Wolfram Sang <wsa@the-dreams.de>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-i2c@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: [PATCH v2 0/2] watchdog: Correct iTCO for Cannon Lake and beyond
Date: Sat, 31 Aug 2019 17:24:00 +0300 [thread overview]
Message-ID: <20190831142402.49736-1-mika.westerberg@linux.intel.com> (raw)
Hi,
Starting from Intel Cannon Lake PCH the NO_REBOOT bit which is required by
the iTCO driver was moved from private register space to be part of the
TCO1_CNT register. This series introduces a new iTCO version (6) that gets
set for Cannon Lake, Cedar Fork, Comet Lake, Elkhart Lake and Ice Lake
which are affected by this move.
The previous version of the series can be found here:
https://lore.kernel.org/linux-watchdog/20190809124553.67012-1-mika.westerberg@linux.intel.com/
Changes from v1:
* Include <linux/bits.h> for BIT()
* Re-organize code so that v4 support is before v6
* Move check for acpi_has_watchdog() to i801_add_tco()
* Added tags from Jean and Guenter.
Mika Westerberg (2):
watchdog: iTCO: Add support for Cannon Lake PCH iTCO
i2c: i801: Use iTCO version 6 in Cannon Lake PCH and beyond
drivers/i2c/busses/i2c-i801.c | 142 +++++++++++++++++++++-------------
drivers/watchdog/iTCO_wdt.c | 26 ++++++-
2 files changed, 112 insertions(+), 56 deletions(-)
--
2.23.0.rc1
next reply other threads:[~2019-08-31 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 14:24 Mika Westerberg [this message]
2019-08-31 14:24 ` [PATCH v2 1/2] watchdog: iTCO: Add support for Cannon Lake PCH iTCO Mika Westerberg
2019-09-03 17:50 ` Wolfram Sang
2019-08-31 14:24 ` [PATCH v2 2/2] i2c: i801: Use iTCO version 6 in Cannon Lake PCH and beyond Mika Westerberg
2019-09-03 17:50 ` Wolfram Sang
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=20190831142402.49736-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.org \
--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;
as well as URLs for NNTP newsgroup(s).