Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753227AbaDYJoI (ORCPT ); Fri, 25 Apr 2014 05:44:08 -0400 Received: from mail-bn1lp0139.outbound.protection.outlook.com ([207.46.163.139]:9345 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751933AbaDYJoB (ORCPT ); Fri, 25 Apr 2014 05:44:01 -0400 Date: Fri, 25 Apr 2014 11:43:43 +0200 From: Anders Berg To: Linus Walleij CC: Arnd Bergmann , Olof Johansson , Mike Turquette , Mark Rutland , Dmitry Eremin-Solenikov , David Woodhouse , Russell King , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v2 3/6] ARM: dts: Device tree for AXM55xx. Message-ID: <20140425094343.GA3160@swsaberg01> References: <2386bd1367aa44741979461358a72dec89608597.1398335771.git.anders.berg@lsi.com> <20140424174741.GA23444@swsaberg01> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: [85.229.45.38] X-ClientProxiedBy: AM3PR02CA006.eurprd02.prod.outlook.com (10.242.240.26) To BLUPR07MB369.namprd07.prod.outlook.com (10.141.26.142) X-Forefront-PRVS: 0192E812EC X-Forefront-Antispam-Report: SFV:NSPM;SFS:(10019001)(6009001)(428001)(51704005)(24454002)(377454003)(199002)(189002)(76482001)(79102001)(42186004)(33656001)(46406003)(76176999)(54356999)(50986999)(74502001)(46102001)(74662001)(4396001)(92566001)(83072002)(92726001)(77982001)(33716001)(97756001)(85852003)(20776003)(47776003)(31966008)(50466002)(99396002)(23726002)(80022001)(81542001)(87976001)(66066001)(80976001)(19580395003)(83322001)(19580405001)(81342001)(83506001)(86362001);DIR:OUT;SFP:1102;SCL:1;SRVR:BLUPR07MB369;H:swsaberg01;FPR:FFF2F8AC.ADC61F09.75FCBE74.C6EEF0D5.20220;MLV:sfv;PTR:InfoNoRecords;A:1;MX:1;LANG:en; X-OriginatorOrg: lsi.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 25, 2014 at 11:16:18AM +0200, Linus Walleij wrote: > On Thu, Apr 24, 2014 at 7:47 PM, Anders Berg wrote: > > On Thu, Apr 24, 2014 at 03:24:14PM +0200, Linus Walleij wrote: > > >> One interrupt per CPU core? > >> > >> The drivers for these blocks will really just grab the first IRQ and > >> then I guess they > >> will only be able to execute on CPU0. > >> > >> It's definately correct to list all the IRQs here, but how do you envision > >> the drivers making use of them in the long run? > > > > It's one interrupt line per input pin (so with the current driver only the first pin > > is usable as interrupt source). > > Hm I'm not sure I understand what a "pin" is in this concept ... > being maintainer of the pin control subsystem and all that really > triggers my interest. > Ok, maybe should replace "pin" with "GPIO" in my previous comment. So, a clarification. In one of the PL061 blocks (named gpio0 in the dts) there is a separate interrupt per GPIO (I assume the motivation here is to enable to control irq affinity per GPIO), where as the other block has a more standard configuration with a single interrupt for all 8 GPIOs in that block. /Anders > Yours. > Linus Walleij > -- 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/