From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Masayuki Ohtak <masa-korg@dsn.okisemi.com>
Cc: meego-dev@meego.com, "Andrew Morton" <akpm@linux-foundation.org>,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Randy Dunlap" <randy.dunlap@oracle.com>,
"Alek Du" <alek.du@intel.com>,
"Richard Röjfors" <richard.rojfors@mocean-labs.com>,
"Mike Frysinger" <vapier@gentoo.org>,
linux-kernel@vger.kernel.org, qi.wang@intel.com,
andrew.chih.howe.khor@intel.com, kok.howg.ewe@intel.com,
joel.clark@intel.com, yong.y.wang@intel.com,
"Tomoya MORINAGA" <morinaga526@dsn.okisemi.com>,
margie.foster@intel.com
Subject: Re: [MeeGo-Dev][PATCH v4] Topcliff: Update PCH_GPIO driver to 2.6.35
Date: Tue, 5 Oct 2010 17:38:09 -0700 [thread overview]
Message-ID: <20101006003808.GA2464@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4CABC02A.9060200@dsn.okisemi.com>
On Wed, Oct 06, 2010 at 09:17:46AM +0900, Masayuki Ohtak wrote:
> GPIO driver of Topcliff PCH
>
> Topcliff PCH is the platform controller hub that is going to be used in
> Intel's upcoming general embedded platform. All IO peripherals in
> Topcliff PCH are actually devices sitting on AMBA bus.
> Topcliff PCH has GPIO I/F. Using this I/F, it is able to access system
> devices connected to GPIO.
>
> Signed-off-by: Masayuki Ohtake <masa-korg@dsn.okisemi.com>
Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2010-10-06 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 0:17 [MeeGo-Dev][PATCH v4] Topcliff: Update PCH_GPIO driver to 2.6.35 Masayuki Ohtak
2010-10-06 0:38 ` Mark Brown [this message]
[not found] ` <000601cb6501$524d2030$66f8800a@maildom.okisemi.com>
2010-10-06 3:56 ` Mark Brown
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=20101006003808.GA2464@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=alek.du@intel.com \
--cc=andrew.chih.howe.khor@intel.com \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=margie.foster@intel.com \
--cc=masa-korg@dsn.okisemi.com \
--cc=meego-dev@meego.com \
--cc=morinaga526@dsn.okisemi.com \
--cc=qi.wang@intel.com \
--cc=randy.dunlap@oracle.com \
--cc=richard.rojfors@mocean-labs.com \
--cc=sameo@linux.intel.com \
--cc=vapier@gentoo.org \
--cc=yong.y.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.