From: Thomas Gleixner <tglx@linutronix.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Moving staging:iio over to threaded interrupts.
Date: Tue, 8 Mar 2011 13:12:17 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1103081304470.2787@localhost6.localdomain6> (raw)
In-Reply-To: <4D76119A.2030100@cam.ac.uk>
On Tue, 8 Mar 2011, Jonathan Cameron wrote:
> On 03/08/11 10:30, Thomas Gleixner wrote:
> > So now you can request the interrupts for your subdevices with
> > request_irq or request_threaded_irq.
> >
> > You can also implement #1 this way, you just mark the sub device
> > interrupts as IRQ_NESTED_THREAD, and then call the handlers from the
> > main trigger irq thread.
> Hi Thomas,
>
> One issue here that I'm not quite sure how to overcome is that the trigger to
> device mapping tends to be dynamic. That is we quite often switch around
> what device is triggered by which trigger at runtime. All done via text label
> matching via sysfs.
Was not aware of that.
> I guess we could maintain this by a spot of indirection and pool of interrupts per
> trigger (with compile time control on how many). Any other approaches come to mind?
That should work. You just need a function in the trigger
implementation which hands back an unused irq number to the device
when a trigger is installed for a device. Then the device calls
request[_threaded]_irq() on that irq number and all should work
magically.
Thanks,
tglx
next prev parent reply other threads:[~2011-03-08 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 17:15 Jonathan Cameron
2011-03-08 10:30 ` Thomas Gleixner
2011-03-08 10:54 ` Jonathan Cameron
2011-03-08 11:23 ` Jonathan Cameron
2011-03-08 12:12 ` Thomas Gleixner [this message]
2011-03-08 12:26 ` Jonathan Cameron
2011-03-15 15:50 ` Jonathan Cameron
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=alpine.LFD.2.00.1103081304470.2787@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®