mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tommy Reynolds <reynolds@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PCI interrupts
Date: Tue, 6 Nov 2001 08:37:49 -0600	[thread overview]
Message-ID: <20011106083749.23fbd03e.reynolds@redhat.com> (raw)
In-Reply-To: <Pine.OSF.4.31.0111052332160.25619-100000@perry>
In-Reply-To: <Pine.OSF.4.31.0111052332160.25619-100000@perry>

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

It was a dark and stormy night.  Suddenly "Matthew Clark" <matt@eee.nott.ac.uk> wrote:

> In my development system the PCI card I am developing  the
> driver for reports (from the PCI config region) that it is using
> interrupt 5.  I can't register this interrupt as it is already
> in use by the USB controller.

PCI interrupts can be shared, but every handler must be registered with the
SA_SHIRQ flag on the request_irq() call.  Both the request_irq() and free_irq()
routines need a "dev_id" cookie to uniquely identify your instance of the
interrurpt handler.

You can see shared interrupts in "/proc/interrupts" because there will be a
comma-separated list of handler names for each IRQ level.

---------------------------------------------+-----------------------------
Tommy Reynolds                               | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone:  +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA  | FAX:    +1.256.837.3839
Senior Software Developer                    | Mobile: +1.919.641.2923

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2001-11-06 14:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05 23:43 Matthew Clark
2001-11-05 23:57 ` Alan Cox
2001-11-06 14:37 ` Tommy Reynolds [this message]
2001-11-06  8:57 Zwane Mwaikambo

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=20011106083749.23fbd03e.reynolds@redhat.com \
    --to=reynolds@redhat.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

all inboxes | Powered by JetHome®