From: Guenter Roeck <linux@roeck-us.net>
To: Peter Tyser <ptyser@xes-inc.com>
Cc: linux-kernel@vger.kernel.org,
James Ralston <james.d.ralston@intel.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 4/8] mfd: lpc_ich: Add support for iTCO v3
Date: Mon, 10 Mar 2014 18:02:40 -0700 [thread overview]
Message-ID: <20140311010240.GD32676@roeck-us.net> (raw)
In-Reply-To: <1394487298-14459-4-git-send-email-ptyser@xes-inc.com>
On Mon, Mar 10, 2014 at 04:34:54PM -0500, Peter Tyser wrote:
> Some newer Atom CPUs, eg Avoton and Bay Trail, use slightly different
> register layouts for the iTCO than the current v1 and v2 iTCO.
> Differences from previous iTCO versions include:
> - The ACPI space is enabled in the "ACPI base address" register instead
> of the "ACPI control register"
>
> - The "no reboot" functionality is set in the "Power Management
> Configuration" register instead of the "General Control and Status"
> (GCS) register or PCI configuration space.
>
> - The "ACPI Control Register" is not present on v3. The "Power
> Management Configuration Base Address" register resides at the same
> address is Avoton/Bay Trail.
>
> To differentiate these newer chipsets create a new v3 iTCO version and
> update the MFD driver to support them.
>
> Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
> Tested-by: Rajat Jain <rajatjain@juniper.net>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: James Ralston <james.d.ralston@intel.com>
> Cc: Samuel Ortiz <sameo@linux.intel.com>
> Cc: Lee Jones <lee.jones@linaro.org>
> Cc: Wim Van Sebroeck <wim@iguana.be>
> Cc: linux-watchdog@vger.kernel.org
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
next prev parent reply other threads:[~2014-03-11 1:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1394487298-14459-1-git-send-email-ptyser@xes-inc.com>
2014-03-10 21:34 ` [PATCH 4/8] mfd: lpc_ich: Add support for iTCO v3 Peter Tyser
2014-03-11 1:02 ` Guenter Roeck [this message]
2014-03-13 22:47 ` Lee Jones
2014-03-15 20:04 ` Wim Van Sebroeck
2014-03-10 21:34 ` [PATCH 5/8] watchdog: iTCO_wdt: Add support for v3 silicon Peter Tyser
2014-03-11 1:06 ` Guenter Roeck
2014-03-13 22:47 ` Lee Jones
2014-03-15 20:03 ` Wim Van Sebroeck
2014-03-18 8:28 ` Lee Jones
2014-03-18 13:59 ` Wim Van Sebroeck
2014-03-18 20:36 ` Lee Jones
2014-03-10 21:34 ` [PATCH 6/8] mfd: lpc_ich: Change Avoton to iTCO v3 Peter Tyser
2014-03-11 1:07 ` Guenter Roeck
2014-03-13 22:48 ` Lee Jones
2014-03-15 20:04 ` Wim Van Sebroeck
2014-03-18 8:27 ` Lee Jones
2014-03-18 14:00 ` Wim Van Sebroeck
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=20140311010240.GD32676@roeck-us.net \
--to=linux@roeck-us.net \
--cc=james.d.ralston@intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=ptyser@xes-inc.com \
--cc=sameo@linux.intel.com \
--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