From: Grant Likely <grant.likely@secretlab.ca>
To: Aaron Sierra <asierra@xes-inc.com>,
Jean Delvare <khali@linux-fr.org>,
Guenter Roeck <guenter@roeck-us.net>
Cc: Peter Tyser <ptyser@xes-inc.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V6 2/3] gpio: Add support for Intel ICHx/3100/Series[56] GPIO
Date: Mon, 12 Mar 2012 11:59:27 -0600 [thread overview]
Message-ID: <20120312175927.19EE33E07B0@localhost> (raw)
In-Reply-To: <886b8cc4-caed-4bce-aa48-9f3181ba09ad@zimbra>
On Wed, 07 Mar 2012 11:41:38 -0600 (CST), Aaron Sierra <asierra@xes-inc.com> wrote:
> From: Peter Tyser <ptyser@xes-inc.com>
>
> This driver works on many Intel chipsets, including the ICH6, ICH7,
> ICH8, ICH9, ICH10, 3100, Series 5/3400 (Ibex Peak), Series 6/C200
> (Cougar Point), and NM10 (Tiger Point).
>
> Additional Intel chipsets should be easily supported if needed, eg the
> ICH1-5, EP80579, etc.
>
> Tested on QM67 (Cougar Point), QM57 (Ibex Peak), 3100 (Whitmore Lake),
> and NM10 (Tiger Point).
>
> Includes work from Jean Delvare:
> - Resource leak removal during module load/unload
> - GPIO API bit value enforcement
>
> Also includes code cleanup from Guenter Roeck and Grant Likely.
>
> Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
> Signed-off-by: Aaron Sierra <asierra@xes-inc.com>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
It looks like this depends on the mfd patch for the header file, so this should
be merged via the mfd tree.
g.
> ---
> MAINTAINERS | 6 +
> drivers/gpio/Kconfig | 13 ++
> drivers/gpio/Makefile | 1 +
> drivers/gpio/gpio-ich.c | 419 +++++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 439 insertions(+), 0 deletions(-)
> create mode 100644 drivers/gpio/gpio-ich.c
>
prev parent reply other threads:[~2012-03-12 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0c695f28-38f7-4f33-bc40-834e0b913f02@zimbra>
2012-03-07 17:41 ` [PATCH V6 2/3] gpio: Add support for Intel ICHx/3100/Series[56] GPIO Aaron Sierra
2012-03-12 17:59 ` Grant Likely [this message]
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=20120312175927.19EE33E07B0@localhost \
--to=grant.likely@secretlab.ca \
--cc=asierra@xes-inc.com \
--cc=guenter@roeck-us.net \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ptyser@xes-inc.com \
/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