Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932435AbWJFQVf (ORCPT ); Fri, 6 Oct 2006 12:21:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932140AbWJFQVe (ORCPT ); Fri, 6 Oct 2006 12:21:34 -0400 Received: from ug-out-1314.google.com ([66.249.92.174]:52529 "EHLO ug-out-1314.google.com") by vger.kernel.org with ESMTP id S932435AbWJFQV3 (ORCPT ); Fri, 6 Oct 2006 12:21:29 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GjWu5A3n+pzeJg2nOnC2PyzE9rcA9rYCeBqtKwB2ou8l389sSjTfV7RSyWhR76m90zTKZjR6unYTXZoIgUTgr0R1TVB9qAJMWlfvASasT/nR9NU9Vv5m8gQG/HvNITuhCKBYSCm/l7+4fsJLFF6AvLL4V82Y1Oicf7UnQjXwvoQ= Message-ID: Date: Fri, 6 Oct 2006 12:21:27 -0400 From: "Dmitry Torokhov" To: "Linus Torvalds" Subject: Re: [PATCH, RAW] IRQ: Maintain irq number globally rather than passing to IRQ handlers Cc: "Jeff Garzik" , "David Howells" , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, "Ingo Molnar" , "Alan Cox" , "Andrew Morton" , "Thomas Gleixner" , "Greg KH" , "David Brownell" , "Alan Stern" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061002132116.2663d7a3.akpm@osdl.org> <20061002162053.17763.26032.stgit@warthog.cambridge.redhat.com> <18975.1160058127@warthog.cambridge.redhat.com> <4525A8D8.9050504@garzik.org> <1160133932.1607.68.camel@localhost.localdomain> <45263ABC.4050604@garzik.org> <20061006111156.GA19678@elte.hu> <45263D9C.9030200@garzik.org> <452673AC.1080602@garzik.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1098 Lines: 26 On 10/6/06, Linus Torvalds wrote: > In contrast, the irq argument itself is really no different from the > cookie we pass in on registration - it's just passing it back to the > driver that requested the thing. So unlike "regs", there's not really > anything strange about it, and there's nothing really "wrong" with having > it there. > > So I'm not at all as convinced about this one. But drivers rarely care about exact IRQ that caused their interrupt routines to be called. I looked at some of them and they normally use it just to print warnings which is not critical (and data can still be retrieved form elsewhere). And without it the only argument can very nicely be passed via a register (if regparm is allowed). Drivers that truly need to know IRQ can have it added to dev_id cookie and use separate dev_ids. -- Dmitry - 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/