From: Samuel Ortiz <sameo@linux.intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org, Viresh Kumar <viresh.kumar@st.com>,
Chris Blair <chris.blair@stericsson.com>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH 2/2 v2] gpio/stmpe: support no-irq mode
Date: Mon, 20 Feb 2012 18:14:53 +0100 [thread overview]
Message-ID: <20120220171453.GH5387@sortiz-mobl> (raw)
In-Reply-To: <1327612635-9171-1-git-send-email-linus.walleij@stericsson.com>
Hi Linus,
On Thu, Jan 26, 2012 at 10:17:15PM +0100, Linus Walleij wrote:
> From: Chris Blair <chris.blair@stericsson.com>
>
> Adds support for boards which have an STMPE GPIO device without the
> interrupt pin connected. This means that no interrupt can be received
> but the GPIO pins can still be driven and read.
>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Acked-by: Viresh Kumar <viresh.kumar@st.com>
> Tested-by: Michel Jaouen <michel.jaouen@stericsson.com>
> Signed-off-by: Chris Blair <chris.blair@stericsson.com>
> ---
> ChangeLog v1->v2:
> - Removes the use of the new no_irq platform data member and
> instead uses the value obtained for the cell irq to know if irqs
> are supported or not. If irqs are not supported, the device
> will not have been given an irq resource and the irq value
> will be invalid.
>
> This depends on the previous patch to the MFD
> code so should better be merged into the MFD tree with the
> previous patch.
Ok, I'm taking this one. It would be nice to get Grant's ACK as well.
Linus, you did not SOB this one. Did you simply forget ?
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2012-02-20 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 21:17 [PATCH 2/2 v2] gpio/stmpe: support no-irq mode Linus Walleij
2012-01-27 4:19 ` Viresh Kumar
2012-02-20 17:14 ` Samuel Ortiz [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=20120220171453.GH5387@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=chris.blair@stericsson.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viresh.kumar@st.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.