From: David Howells <dhowells@redhat.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@osdl.org>,
linux-arch@vger.kernel.org
Subject: Re: irq-type-flags.patch
Date: Wed, 09 Nov 2005 15:13:47 +0000 [thread overview]
Message-ID: <7224.1131549227@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20051109132449.GC4712@flint.arm.linux.org.uk>
Russell King <rmk@arm.linux.org.uk> wrote:
> Neither the arch not the bus dictates what the
> device manufacturer decides to do with their interrupt output.
On the other hand, the device manufacturer does not decree what the arch and
supporting chipset will *accept*. There's no guarantee that all trigger types
will be supported. For instance on my ASB2305 board, I've got an on-chip PIC
that will accept any of the four trigger types, but the PCI bus interrupt line
attached to one of the external interrupt pins will *only* accept low-level
triggered. In such a case, the bus *must* override anything set by one of the
devices.
David
next prev parent reply other threads:[~2005-11-09 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 3:10 irq-type-flags.patch Andrew Morton
2005-11-09 9:26 ` irq-type-flags.patch William Lee Irwin III
2005-11-09 13:20 ` irq-type-flags.patch David Howells
2005-11-09 13:24 ` irq-type-flags.patch Russell King
2005-11-09 15:13 ` David Howells [this message]
2005-11-09 15:27 ` irq-type-flags.patch Russell King
2005-11-09 16:07 ` irq-type-flags.patch David Howells
2005-11-09 13:30 ` irq-type-flags.patch Paul Mundt
2005-11-09 13:49 ` irq-type-flags.patch Matthew Wilcox
2005-11-09 14:40 ` irq-type-flags.patch Paul Mundt
2005-11-09 14:47 ` irq-type-flags.patch Russell King
2005-11-09 15:26 ` irq-type-flags.patch Matthew Wilcox
2005-11-09 15:28 ` irq-type-flags.patch Russell King
2005-11-10 14:06 ` irq-type-flags.patch Andi Kleen
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=7224.1131549227@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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