Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756925Ab2HJItU (ORCPT ); Fri, 10 Aug 2012 04:49:20 -0400 Received: from moutng.kundenserver.de ([212.227.17.9]:60795 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752606Ab2HJItR (ORCPT ); Fri, 10 Aug 2012 04:49:17 -0400 Date: Fri, 10 Aug 2012 10:48:59 +0200 From: Thierry Reding To: Linus Walleij Cc: Russell King - ARM Linux , Grant Likely , Arnd Bergmann , linux-kernel@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, Linus Walleij , Rob Herring , Wolfram Sang Subject: Re: [PATCH v2] gpio: Add Avionic Design N-bit GPIO expander support Message-ID: <20120810084859.GA16550@avionic-0098.mockup.avionic-design.de> References: <1343044770-6591-1-git-send-email-thierry.reding@avionic-design.de> <20120809202054.GA24503@avionic-0098.mockup.avionic-design.de> <20120810083508.GA16251@avionic-0098.mockup.avionic-design.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V02:K0:7T/a+4te38fN/0M5DeAWDrn4UYIPXGkgmYOSps3qqsS B/hASiKhiQO3ztgzyqtRtllHURxDxW1bfy05v5bF3pskfcDVFw 8pZ5wllv522D2ZMJGGy5ztJ2deblrtmUWoMHWOGxbG+3TX2/Fw HQ3CTZXJIuK3BOppf4RAXdxd7G7n2UoVP5E7a8023jozusyz0J meVM4p4XGNjQPMyLWTRmCbbOs9uq6zFJvkxoEy7+XWXJNFPBUR NMmBYggAXh8ybq1/d3qGRtfYm23domusQP3WRT7Tttw60WlP4g peE+hAmHRPIvayEvLb41dV2AnDoX8qStCwcQHsMaXlU7Xy7RRo WjZQm2hKC00ltuYo+zavkD87myA8M2UtdQX2VJqTVt84I3E7p7 BgRa6mD71tA5y+an5VygJi/mgU3RQEQ0vM= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2552 Lines: 67 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 10, 2012 at 10:41:58AM +0200, Linus Walleij wrote: > On Fri, Aug 10, 2012 at 10:35 AM, Thierry Reding > wrote: > >> Consult the following article on LWN: > >> http://lwn.net/Articles/470820/ > >> > >> Then grep your gitlog and you'll see we got rid of it from ARM. > > > > Then why is there still the following in arch/arm/include/asm/irq.h? > > > > /* > > * Use this value to indicate lack of interrupt > > * capability > > */ > > #ifndef NO_IRQ > > #define NO_IRQ ((unsigned int)(-1)) > > #endif >=20 > That's a question for Russell but I think it's basically there for > old platforms, on a "don't use it"-basis. (Maybe a comment could > be good.) >=20 > As you see non-sparse platforms can redefine NO_IRQS in their > file, but in practice things like the VIC and GIC > drivers have been switched over to using irqdomain which > in turn does *not* allow IRQ 0 to be used, so most platforms > are indirectly disallowed to use IRQ 0 anyway. In fact I think > some of them are just broken now. In that case it might be better to just drop it altogether and wait until people with the broken platforms start complaining. Thierry --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJQJMr7AAoJEN0jrNd/PrOhlZ8QAIZ8855/Wm9g5454USc2T8zv PyM8+aOF9dSCiQBcZb8BG6A+figj60DhcEZtoVCzni9IrQHJY0NKZhOpCro9qinz A61QQ7GjvEvNOpp/wbtG+BUNmFCRSGn5gGhszMlsngMVIrOerGNmwlT+A1F95Sqz kaIUS636qOJaPucTYD9rgin3UIesoZmrzxwE8fdflx93lV4xYXzdYWkZXZey8Nx1 D1oLLU6MLjQwQvKix5XBu0CNCP0Xe2og0GTKJtuqI8sbQNunxzYIGzEeUDUvH6Qa 0duXUhxbc3vsVgtn1BmBWMT5Cy7ppi3UIYzdujIRmBChBl1Sj8O+KG1tBBv4pvVD Tyj0pt1q8M22KRsS5pT5O29OwP8Wnb7Q8UqTona5f88T7KTjD59GC/0/cFilYELO Z4+I38+HNUuUBfoQo1r2ZKtvQhuTYkXOULAY+sARFycaiAx6n+F0WmNRnpiNRjgY EPjTIFp+MqBTRhEWFZln+Xcv7FSXAleSDyVJfGQhTjFoUTO1RaAAUecdpXkAKCLs 1K5NHadOSyVcoVoo5MdalludVpjTHnpyhGzI+RUfFb1USzIhZH+m+SsNAG7nKYpi YsHSufdRohdA+DsSKaGu/oEMxsVLdHMNw7bLv01Plrk+4j4yx7iswxFSOs2+TQg0 qQDY4iEL6wFTzxYkyukn =TiLA -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- -- 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/