Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755073Ab0KXNuw (ORCPT ); Wed, 24 Nov 2010 08:50:52 -0500 Received: from cassiel.sirena.org.uk ([80.68.93.111]:52533 "EHLO cassiel.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754614Ab0KXNuv (ORCPT ); Wed, 24 Nov 2010 08:50:51 -0500 Date: Wed, 24 Nov 2010 13:50:49 +0000 From: Mark Brown To: Haojian Zhuang Cc: Thomas Gleixner , linux-kernel , linux-arm-kernel Subject: Re: [question] NR_IRQS in genirq Message-ID: <20101124135048.GC13507@sirena.org.uk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Cookie: I invented skydiving in 1989! User-Agent: Mutt/1.5.18 (2008-05-17) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: broonie@sirena.org.uk X-SA-Exim-Scanned: No (on cassiel.sirena.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 808 Lines: 16 On Wed, Nov 24, 2010 at 09:46:06PM +0800, Haojian Zhuang wrote: > My hardware environment is ARM. Each machine description can specify > nr_irqs. In my implementation of PXA, NR_IRQS is fixed for SoC > internal IRQs. And there's some additional board IRQs, we arrange them > between NR_IRQS and nr_irqs. So nr_irqs will be larger than NR_IRQS if > board IRQs exists. Most ARM platforms have come up with some Kconfig gunk to allow boards to extend this for off-SoC GPIOs. It'd be really nice to get rid of NR_IRQS and stop having to worry about this at all :( -- 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/