[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Shared Interrupt handling.

To: k b <k_bisla@xxxxxxxxxxx>
Subject: Re: Shared Interrupt handling.
From: Greg KH <greg@xxxxxxxxx>
Date: Wed, 2 May 2007 19:12:33 -0700
Cc: kernelnewbies@xxxxxxxxxxxx
In-reply-to: <BAY105-F5E672F5F643DD0A20A78A8E410@phx.gbl>
List-archive: <http://mail.nl.linux.org/kernelnewbies/>
List-help: <mailto:ecartis@nl.linux.org?Subject=help>
List-id: <kernelnewbies.nl.linux.org>
List-owner: <mailto:ecartis-owner@nl.linux.org>
List-post: <mailto:kernelnewbies@nl.linux.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=subscribe>
List-unsubscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=unsubscribe>
References: <20070502224356.GA22143@gateway.home> <BAY105-F5E672F5F643DD0A20A78A8E410@phx.gbl>
Reply-to: kernelnewbies <kernelnewbies@xxxxxxxxxxxx>
Sender: kernelnewbies-bounce@xxxxxxxxxxxx
User-agent: Mutt/1.5.15 (2007-04-06)

On Wed, May 02, 2007 at 06:23:46PM -0700, k b wrote:
>  Hi,
>  Can someone explain how the kernel figures out which interrupt handler
>  to call when the interrupt line is shared.

It calles them all, until one says it handled the interrupt.

thanks,

greg k-h

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ

Follow-Ups:
- Re: Shared Interrupt handling.
  - From: Rajat Jain

References:
- Re: is anyone seriously using execute-in-place (in embedded systems)?
  - From: Erik Mouw
- Shared Interrupt handling.
  - From: k b

Prev by Date: Re: Shared Interrupt handling.
Next by Date: RE: Shared Interrupt handling.
Previous by thread: Re: Shared Interrupt handling.
Next by thread: Re: Shared Interrupt handling.
Index(es):
- Date
- Thread