From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Cox <alan@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] gpio: Add PMIC GPIO block support
Date: Thu, 22 Jul 2010 16:01:41 +0100 [thread overview]
Message-ID: <20100722150141.GA25002@srcf.ucam.org> (raw)
In-Reply-To: <20100713095544.3064.80122.stgit@localhost.localdomain>
On Tue, Jul 13, 2010 at 10:56:25AM +0100, Alan Cox wrote:
> From: Alek Du <alek.du@intel.com>
>
> Moorestown has PMIC chip which contains GPIO blocks. The PMIC chip is
> connected to Langwell by SPI interface. So this GPIO driver will be regarded
> as SPI GPIO expander though the actual GPIO access is through IPC and SRAM.
> The SPI master contoller will probe this device driver by parsing SPIB table.
>
> Cleaned up for new IPC, GPE removed and some printk and other tidying by
> Alan Cox. Fixes for points noted by Matthew Garrett
Applied with some whitespace cleanup.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-07-22 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 9:56 [PATCH] gpio: Add PMIC GPIO block support Alan Cox
2010-07-22 15:01 ` Matthew Garrett [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-08 17:09 Alan Cox
2010-07-08 19:37 ` Matthew Garrett
2010-07-09 13:35 ` Alan Cox
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=20100722150141.GA25002@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alan@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
/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