From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Samuel Ortiz <sameo@liniux.intel.com>,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] mfd: Still check other interrupts if we get a wm831x touchscreen IRQ
Date: Mon, 9 Jan 2012 00:23:26 +0100 [thread overview]
Message-ID: <20120108232326.GF13679@sortiz-mobl> (raw)
In-Reply-To: <1325006410-22147-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Hi Mark,
On Tue, Dec 27, 2011 at 05:20:10PM +0000, Mark Brown wrote:
> It is possible that we will see another interrupt triggering at the same
> time as the touchscreen interrupts so it's still worth checking other
> possible sources. Almost all of the win from the fast path comes from only
> needing to read the primary register and saving the I/O costs.
Thanks, applied.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2012-01-08 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 17:20 [PATCH] mfd: Still check other interrupts if we get a wm831x touchscreen IRQ Mark Brown
2012-01-08 23:23 ` 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=20120108232326.GF13679@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@liniux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox