From: Samuel Ortiz <sameo@linux.intel.com>
To: Denis Turischev <denis@compulab.co.il>
Cc: LKML <linux-kernel@vger.kernel.org>,
Grant Likely <grant.likely@secretlab.ca>,
David Brownell <dbrownell@users.sourceforge.net>
Subject: Re: [PATCH 3/3 v2] sch_gpio: expand for Tunnel Creek
Date: Mon, 14 Mar 2011 12:45:40 +0100 [thread overview]
Message-ID: <20110314114540.GO31153@sortiz-mobl> (raw)
In-Reply-To: <4D7DF391.50302@compulab.co.il>
Hi Denis,
On Mon, Mar 14, 2011 at 12:53:05PM +0200, Denis Turischev wrote:
> Almost the same driver for both Poulsbo and Tunnel Creek.
> The difference is in quantity of GPIOs powered by the core power
> rail and by suspend power supply, default values for some GPIOs, etc.
> Detect actual hardware by platform device ID assigned in lpc_sch
> and set configuration accordingly.
Grant, are you ok with me taking this patch ?
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2011-03-14 11:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-13 15:26 [PATCH 1/3] pci_ids: add Intel Tunnel Creek LPC Bridge device ID Denis Turischev
2011-03-13 15:28 ` [PATCH 2/3] lpc_sch: expand for Tunnel Creek Denis Turischev
2011-03-13 15:30 ` [PATCH 3/3] sch_gpio: expand for Tunnel Creak Denis Turischev
2011-03-14 10:53 ` [PATCH 3/3 v2] sch_gpio: expand for Tunnel Creek Denis Turischev
2011-03-14 11:45 ` Samuel Ortiz [this message]
2011-03-14 19:20 ` Grant Likely
2011-03-17 23:13 ` [PATCH 3/3] sch_gpio: expand for Tunnel Creak Samuel Ortiz
2011-03-17 23:12 ` [PATCH 2/3] lpc_sch: expand for Tunnel Creek Samuel Ortiz
2011-03-14 11:43 ` [PATCH 1/3] pci_ids: add Intel Tunnel Creek LPC Bridge device ID Samuel Ortiz
2011-03-14 15:50 ` Jesse Barnes
2011-03-17 23:11 ` Samuel Ortiz
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=20110314114540.GO31153@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=dbrownell@users.sourceforge.net \
--cc=denis@compulab.co.il \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@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