From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
linux-omap@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Balaji T K <balajitk@ti.com>, Rajendra Nayak <rnayak@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] mfd: speedup twl4030 irq response time and decrease irq disable time
Date: Mon, 27 Sep 2010 22:12:26 -0700 [thread overview]
Message-ID: <20100928051225.GA9864@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTimT8WkgiCANL4tXcNgnm63oMnO2d2bKjDD1chJv@mail.gmail.com>
On Tue, Sep 28, 2010 at 01:01:32PM +0800, Ming Lei wrote:
> 2010/9/28 Mark Brown <broonie@opensource.wolfsonmicro.com>:
> > Have you raised this issue with the genirq guys? This sounds like
> > something that the core infrastructure should be able to cope with.
> Even genirq guys can help us to convert to irq thread framework, I
> don't think there is good way to set priority for one irq thread.
What I'm saying is that this sounds like something it's reasonable to
want to do so if there's no way currently to get high priority handling
of timing sensitive interrupt controllers it'd be good if there could
be.
prev parent reply other threads:[~2010-09-28 5:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 1:49 [PATCH] mfd: speedup twl4030 irq response time and decrease irq disable time tom.leiming
2010-09-27 14:31 ` Ming Lei
2010-09-27 15:48 ` Samuel Ortiz
2010-09-28 0:25 ` Ming Lei
2010-09-28 4:24 ` Mark Brown
2010-09-28 5:01 ` Ming Lei
2010-09-28 5:12 ` Mark Brown [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=20100928051225.GA9864@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=balajitk@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rnayak@ti.com \
--cc=sameo@linux.intel.com \
--cc=santosh.shilimkar@ti.com \
--cc=tglx@linutronix.de \
--cc=tom.leiming@gmail.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;
as well as URLs for NNTP newsgroup(s).