From: Robert Hancock <hancockr@shaw.ca>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: de2104x: interrupts before interrupt handler is registered
Date: Tue, 07 Mar 2006 18:05:04 -0600 [thread overview]
Message-ID: <440E1FB0.6030300@shaw.ca> (raw)
In-Reply-To: <Pine.LNX.4.61.0603071306070.9728@chaos.analogic.com>
linux-os (Dick Johnson) wrote:
> There are now other "standard" boards that seem to be experiencing
> the same problem. Maybe it is time to make a procedure that turns
> off interrupts for a specific device (not an unknown IRQ). Then
> a subsequent call turns them on after the handler is in place.
> This wouldn't affect current drivers. They would still turn on
> hot by default.
How do you propose to do this? There's no way to mask interrupts from
just one device which is sharing an IRQ line, you have to mask
interrupts from all of those devices. That would be quite ugly IMHO if
one device could disable the interrupt used by another device for
however long it felt like.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2006-03-08 0:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5N5Ql-30C-11@gated-at.bofh.it>
[not found] ` <5NnDE-44v-11@gated-at.bofh.it>
2006-03-07 0:02 ` de2104x: interrupts before interrupt handler is registered Robert Hancock
2006-03-07 12:07 ` linux-os (Dick Johnson)
2006-03-07 13:58 ` Robert Hancock
2006-03-07 14:21 ` linux-os (Dick Johnson)
2006-03-07 17:51 ` Bjorn Helgaas
2006-03-07 18:17 ` linux-os (Dick Johnson)
2006-03-08 0:05 ` Robert Hancock [this message]
2006-03-08 8:18 ` Jesse Brandeburg
2006-03-08 16:05 ` Bjorn Helgaas
2006-03-08 19:34 ` Martin Michlmayr
2006-03-08 0:00 ` Robert Hancock
2006-03-08 12:03 ` linux-os (Dick Johnson)
2006-03-08 23:34 ` Robert Hancock
2006-03-09 12:42 ` linux-os (Dick Johnson)
[not found] <5Nz1Y-4hZ-25@gated-at.bofh.it>
[not found] ` <5NKTG-4F7-21@gated-at.bofh.it>
[not found] ` <5NLmp-5sk-5@gated-at.bofh.it>
[not found] ` <5NODG-1RH-3@gated-at.bofh.it>
[not found] ` <5O23T-59S-15@gated-at.bofh.it>
2006-03-09 0:02 ` Robert Hancock
2006-03-05 18:07 Martin Michlmayr
2006-03-05 18:59 ` Francois Romieu
2006-03-06 14:35 ` Martin Michlmayr
2006-03-06 19:17 ` Martin Michlmayr
2006-03-06 19:48 ` Francois Romieu
2006-03-06 19:59 ` Martin Michlmayr
2006-03-06 20:23 ` Francois Romieu
2006-03-06 20:29 ` Martin Michlmayr
2006-03-06 20:54 ` Francois Romieu
2006-03-07 5:16 ` Martin Michlmayr
2006-03-06 21:17 ` Francois Romieu
2006-03-07 5:11 ` Martin Michlmayr
2006-03-07 14:57 ` Martin Michlmayr
2006-03-08 0:15 ` Francois Romieu
2006-03-08 3:22 ` Martin Michlmayr
2006-03-07 15:16 ` Martin Michlmayr
2006-03-06 13:02 ` linux-os (Dick Johnson)
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=440E1FB0.6030300@shaw.ca \
--to=hancockr@shaw.ca \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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