linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Arce, Abraham" <x0066660@ti.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC] [PATCH 1/3] OMAP4: Keyboard Controller Support
Date: Tue, 11 May 2010 14:39:53 -0700	[thread overview]
Message-ID: <87632ut8wm.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100511164136.GA7396@core.coreip.homeip.net> (Dmitry Torokhov's message of "Tue\, 11 May 2010 09\:41\:37 -0700")

Dmitry Torokhov <dmitry.torokhov@gmail.com> writes:

> On Tue, May 11, 2010 at 07:53:23AM -0700, Kevin Hilman wrote:
>> Dmitry Torokhov <dmitry.torokhov@gmail.com> writes:
>> 
>> > On Tue, May 11, 2010 at 12:03:44AM -0500, Arce, Abraham wrote:
>> >> Hi again Dmitry,
>> >> 
>> >> > No worries, although at first I was surprised that Trilok spoke exactly
>> >> > the same words I did ;)
>> >> > 
>> >> 
>> >> :)
>> >> 
>> >> > > > > > +
>> >> > > > > > +/* Interrupt thread handler thread */
>> >> > > > > > +
>> >> > > > > > +static irqreturn_t omap_keypad_threaded(int irq, void *dev_id)
>> >> > > > > > +{
>> >> > > > >
>> >> > > > > Why is iti threaded? I fo not see anything that will sleep.
>> >> > >
>> >> > >
>> >> > > It was implemented based on previous comments...
>> >> > >
>> >> > 
>> >> > Would you point me to that comment? Like I said, I do not see anything
>> >> > that would possibly sleep in this routine so you don't need to use
>> >> > threaded interrupt.
>> >> 
>> >> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg26352.html
>> >> 
>> >
>> > Thanks.
>> >
>> > I think Kevin meant "use theaded IRQ, wherever possible" [if we need
>> > to sleep in interrupt handler].
>> 
>> Actually, even interrupts that don't sleep can use threaded IRQs.  I
>> prefer to see threaded IRQs wherever possible.  Especially since we're
>> moving towards a world where all interrupts are run with interrupts
>> disabled, using threaded IRQs minimizes interrupts-off critical
>> sections.
>> 
>
> I think in this case threaded IRQ would just add unnecessary overhead.
> There are no scanning delays, just a few register reads and writes.
> Input core will take some cycles propagating the events but it disables
> interrupts anyway. Setting up a separate thread and scheduling does not
> make much sense here.
>
> Also I am not sure if arches with large number of interrupts would want
> to move to all threaded interrupts model.

OK, it's your call for this subsystem.

Kevin

  reply	other threads:[~2010-05-11 21:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14  1:10 [RFC] [PATCH 1/3] OMAP4: Keyboard Controller Support Arce, Abraham
2010-04-14  7:34 ` Trilok Soni
2010-04-16  0:04   ` Arce, Abraham
2010-04-20 23:11     ` Kevin Hilman
2010-04-16  5:06 ` Felipe Balbi
2010-05-05 23:17   ` Arce, Abraham
2010-04-20 23:16 ` Kevin Hilman
2010-05-06  2:30   ` Arce, Abraham
2010-04-21  6:55 ` Dmitry Torokhov
2010-05-11  4:13   ` Arce, Abraham
2010-05-11  4:17     ` Arce, Abraham
2010-05-11  4:41       ` Dmitry Torokhov
2010-05-11  5:03         ` Arce, Abraham
2010-05-11  5:45           ` Dmitry Torokhov
2010-05-11 14:53             ` Kevin Hilman
2010-05-11 16:41               ` Dmitry Torokhov
2010-05-11 21:39                 ` Kevin Hilman [this message]
2010-05-12  5:34                   ` Shilimkar, Santosh
2010-05-12  5:40         ` Arce, Abraham
2010-05-12  5:45           ` Shilimkar, Santosh
2010-05-12  6:03             ` Dmitry Torokhov
2010-05-12  6:19               ` Shilimkar, Santosh
2010-05-12  6:35                 ` Dmitry Torokhov
2010-05-12  6:54                   ` Shilimkar, Santosh
2010-05-12  6:20               ` Arce, Abraham

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=87632ut8wm.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=x0066660@ti.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).