Date: Thu, 14 Dec 2006 11:33:11 +0000
From: Alan <alan@lxorguk.ukuu.org.uk>
To: tglx@linutronix.de
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
       Linus Torvalds <torvalds@osdl.org>, Greg KH <gregkh@suse.de>,
       Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] more Driver core patches for 2.6.19
Message-ID: <20061214113311.24ba9b7f@localhost.localdomain>
In-Reply-To: <1166087742.29505.79.camel@localhost.localdomain>
References: <20061213195226.GA6736@kroah.com>
	<Pine.LNX.4.64.0612131205360.5718@woody.osdl.org>
	<1166044471.11914.195.camel@localhost.localdomain>
	<Pine.LNX.4.64.0612131323380.5718@woody.osdl.org>
	<1166048081.11914.208.camel@localhost.localdomain>
	<1166049055.29505.47.camel@localhost.localdomain>
	<20061213235601.2a565229@localhost.localdomain>
	<1166087742.29505.79.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 947
Lines: 28

> > IRQ is shared with the disk driver, box dead.
> 
> Err ? 
> 
> IRQ happens
> 
> IRQ is disabled by the generic handling code
> 
> Handler is invoked and checks, whether the irq is from the device or
> not. 
>  - If not, it returns IRQ_NONE, so the next driver (e.g. disk) is
> invoked.
>  - If yes, it masks the chip on the device, which disables the chip
> interrupt line and returns IRQ_HANDLED.
> 
> In both cases the IRQ gets reenabled from the generic irq handling code
> on return, so why is the box dead ?

I wrote this before your "generic" layer was in fact explained further to
not be generic at all and involve a new driver for each device. Your
original explanation was not clear.

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/