Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756528Ab0A0Xb5 (ORCPT ); Wed, 27 Jan 2010 18:31:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756509Ab0A0Xb5 (ORCPT ); Wed, 27 Jan 2010 18:31:57 -0500 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:52302 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753727Ab0A0Xb4 (ORCPT ); Wed, 27 Jan 2010 18:31:56 -0500 Date: Wed, 27 Jan 2010 23:29:55 +0000 From: Russell King - ARM Linux To: adharmap@codeaurora.org Cc: linux-arm-kernel@lists.infradead.org, Ingo Molnar , Catalin Marinas , Yinghai Lu , Tony Lindgren , Santosh Shilimkar , Kevin Hilman , Kalle Valo , Jean Pihet , Linus Walleij , Colin Tuckley , Philby John , Srinidhi Kasagar , Alessandro Rubini , Andrea Gallo , linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, Abhijeet Dharmapurikar Subject: Re: [RFC PATCH 5/5] gic: initialize interrupts as per argument Message-ID: <20100127232955.GG29665@n2100.arm.linux.org.uk> References: <1264620749-24527-1-git-send-email-adharmap@codeaurora.org> <1264620749-24527-6-git-send-email-adharmap@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1264620749-24527-6-git-send-email-adharmap@codeaurora.org> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1205 Lines: 25 On Wed, Jan 27, 2010 at 11:32:29AM -0800, adharmap@codeaurora.org wrote: > From: Abhijeet Dharmapurikar > > Initialize interrupts as per an argument passed instead of initializing > them as active level low triggered interrupts. > > Signed-off-by: Abhijeet Dharmapurikar > --- > Configuring level triggered interrupts as default may not be correct on > some platforms, this changes the default behaviour of the gic_dist_init > function and also adds a flag to indicate whether the default should be level > or edge. Changing the interrupt type for all interrupts is just wrong. For on-chip peripherals, you generally want to use level based interrupts as they're the most efficient and simplest way to signal interrupts. It should be a per-interrupt thing, and we already have that through request_irq() etc. Other platforms manage this just fine without having to have special configuration like this. -- 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/