public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
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 16:07:13 +0000	[thread overview]
Message-ID: <9150.1131552433@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20051109152727.GG4712@flint.arm.linux.org.uk>

Russell King <rmk@arm.linux.org.uk> wrote:

> I think the root of this issue is that you're thinking that the driver
> uses this to dictate to the interrupt controller what it wants the
> controller to program itself for.  It's more a case that the driver is
> saying "my device produces this kind of interrupt, please configure
> the input appropriately."

Okay.

Still, I'd like to see some handling for a mismatch - the case in which the
driver says "my device can produce X" but X isn't available with that PIC/bus
combination. Or maybe provide a way (if there isn't one already) for the
driver to query the available trigger types. Some devices I've come across
have configurable interrupt generators.

David

  reply	other threads:[~2005-11-09 16:07 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     ` irq-type-flags.patch David Howells
2005-11-09 15:27       ` irq-type-flags.patch Russell King
2005-11-09 16:07         ` David Howells [this message]
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=9150.1131552433@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