From: Abramo Bagnara <abramo@alsa-project.org>
To: D.A.Fedorov@inp.nsk.su
Cc: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>,
Balbir Singh <balbir_soni@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: Is it useful to support user level drivers
Date: Thu, 21 Jun 2001 18:34:44 +0200 [thread overview]
Message-ID: <3B322224.91E17820@alsa-project.org> (raw)
In-Reply-To: <Pine.SGI.4.10.10106212130280.3193032-100000@Sky.inp.nsk.su>
"Dmitry A. Fedorov" wrote:
>
> On Thu, 21 Jun 2001, Oliver Neukum wrote:
>
> > > Lastly an IRQ kernel module can disable_irq() from interrupt handler
> > > and enable it again only on explicit acknowledge from user.
> >
> > Unless you need that interrupt to be enabled to deliver the signal or let
>
> Need not. Signal and other event delivery mechanisms has nothing
> common with disable/enable_irq().
>
> > userspace reenable the interrupt.
>
> "user acknowledge" is mean that.
>
> > In addition, how do you handle shared interrupts ?
>
> It is impossible, see my another message.
I don't see why you think it's impossible, the only thing you need is
that your kernel module know how to discriminate the interrupt source.
You can do this also with a irq.o module and other tiny modules that
register their irq source detection code.
Then you have /dev/irqX with the following API:
- ioctl(fd, IRQ_SUBSCRIBE, source_id);
- ioctl(fd, IRQ_ACK, source_id);
- poll
- async notification
Interrupts received between notification and acknowledge are queued
(i.e. counted). An alternative to queuing (user selectable) is to block
interrupt generation at hardware level in kernel space immediately
before notification.
I'm missing something?
--
Abramo Bagnara mailto:abramo@alsa-project.org
Opera Unica Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy
ALSA project http://www.alsa-project.org
It sounds good!
next prev parent reply other threads:[~2001-06-21 16:36 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 10:41 Is it useful to support user level drivers Balbir Singh
2001-06-21 10:55 ` Tim Waugh
2001-06-21 11:04 ` Alan Cox
2001-06-21 12:43 ` Balbir Singh
2001-06-21 13:27 ` Alan Cox
2001-06-28 22:52 ` Pavel Machek
2001-06-21 12:45 ` Dmitry A. Fedorov
2001-06-21 13:24 ` Oliver Neukum
2001-06-21 14:46 ` Dmitry A. Fedorov
2001-06-21 15:19 ` Oliver Neukum
2001-06-22 4:19 ` Dmitry A. Fedorov
2001-06-22 7:28 ` Balbir Singh
2001-06-21 16:34 ` Abramo Bagnara [this message]
2001-06-21 17:27 ` Alan Cox
2001-06-21 19:59 ` Abramo Bagnara
2001-06-21 20:40 ` Richard B. Johnson
2001-06-21 20:54 ` Abramo Bagnara
2001-06-21 21:09 ` Oliver Neukum
2001-06-28 22:57 ` Pavel Machek
2001-06-21 13:28 ` Alan Cox
2001-06-21 14:03 ` Matthias Urlichs
2001-06-28 22:54 ` Pavel Machek
2001-06-21 14:20 ` Dmitry A. Fedorov
2001-06-21 11:38 ` Dmitry A. Fedorov
2001-06-21 13:50 ` john slee
2001-06-21 13:58 ` Matthias Urlichs
2001-06-21 14:21 ` john slee
2001-06-28 22:51 ` Pavel Machek
[not found] <mailman.993156181.18994.linux-kernel2news@redhat.com>
2001-06-21 22:06 ` Pete Zaitcev
2001-06-21 22:20 ` David S. Miller
2001-06-21 23:09 ` Mike Mackovitch
2001-06-21 23:22 ` David S. Miller
2001-06-21 23:50 ` Mike Mackovitch
2001-06-22 0:36 ` David S. Miller
2001-06-21 23:40 ` Richard B. Johnson
2001-06-22 0:30 ` Anders Larsen
2001-06-22 0:43 ` Richard B. Johnson
2001-06-25 0:06 ` Anders Larsen
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=3B322224.91E17820@alsa-project.org \
--to=abramo@alsa-project.org \
--cc=D.A.Fedorov@inp.nsk.su \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=balbir_soni@yahoo.com \
--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