From: Samuel Ortiz <sameo@linux.intel.com>
To: tom.leiming@gmail.com
Cc: 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
Subject: Re: [PATCH] mfd: speedup twl4030 irq response time and decrease irq disable time
Date: Mon, 27 Sep 2010 17:48:10 +0200 [thread overview]
Message-ID: <20100927154809.GI2560@sortiz-mobl> (raw)
In-Reply-To: <1285120171-3030-1-git-send-email-tom.leiming@gmail.com>
Hi Tom,
On Wed, Sep 22, 2010 at 09:49:31AM +0800, tom.leiming@gmail.com wrote:
> From: Ming Lei <tom.leiming@gmail.com>
>
> This patch sets scheduler policy of twl4030 irq thread
> (twl4030_irq_thread) as SCHED_FIFO to speedup irq response
> time, just like taken by kernel threaded irq in irq_thread
> (kernel/irq/manage.c). Also higher priority than that of
> threaded irq is taken to avoid preemption from twl4030
> subchips's threaded irq handler, so pih irq disable time may
> be decreased.
Wouldn't converting your twl4030_irq_thread() to the threaded IRQ framework
fix that problem ?
> The pih irq is disabled in handle_twl4030_pih which may
> wakeup twl4030 irq thread, and the pih irq will be enabled
> again until complete of all sih irqs' handling in twl4030
> irq thread.
>
> Also for each one interrupt line of twl4030 subchip, only
> two irq events can be buffered by twl4030(4.4.2.3 of TPS65950 TRM).
Could you explain how is that related to the patch below ?
Cheers,
Samuel.
> Signed-off-by: Ming Lei <tom.leiming@gmail.com>
> Cc: Samuel Ortiz <sameo@linux.intel.com>
> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: Balaji T K <balajitk@ti.com>
> Cc: Rajendra Nayak <rnayak@ti.com>
> Cc: Kevin Hilman <khilman@deeprootsystems.com>
> Cc: linux-kernel@vger.kernel.org
> ---
> drivers/mfd/twl4030-irq.c | 10 +++++++++-
> 1 files changed, 9 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mfd/twl4030-irq.c b/drivers/mfd/twl4030-irq.c
> index 097f24d..d1e0d80 100644
> --- a/drivers/mfd/twl4030-irq.c
> +++ b/drivers/mfd/twl4030-irq.c
> @@ -286,8 +286,16 @@ static int twl4030_irq_thread(void *data)
> long irq = (long)data;
> static unsigned i2c_errors;
> static const unsigned max_i2c_errors = 100;
> -
> -
> + struct sched_param param = {
> + .sched_priority = MAX_USER_RT_PRIO/2 + 10,
> + };
> +
> + /* Take higher priority than threaded irq to make us immune of
> + * preemption from twl4030 subchips's threaded irq handler, then
> + * we can complete all SIH irqs' handling and enable PIH irq
> + * again asap.
> + * */
> + sched_setscheduler(current, SCHED_FIFO, ¶m);
> current->flags |= PF_NOFREEZE;
>
> while (!kthread_should_stop()) {
> --
> 1.6.2.5
>
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2010-09-27 15:48 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 [this message]
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
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=20100927154809.GI2560@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=balajitk@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--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).