Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761668Ab3IDUS6 (ORCPT ); Wed, 4 Sep 2013 16:18:58 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:42495 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759617Ab3IDUS4 (ORCPT ); Wed, 4 Sep 2013 16:18:56 -0400 Message-ID: <522795AB.3060303@wwwdotorg.org> Date: Wed, 04 Sep 2013 14:18:51 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8 MIME-Version: 1.0 To: Lars Poeschel CC: Linus Walleij , Lars Poeschel , Grant Likely , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , Mark Rutland , Ian Campbell , Kumar Gala , Pawel Moll , Tomasz Figa , Javier Martinez Canillas , Enric Balletbo i Serra , Jean-Christophe PLAGNIOL-VILLARD , Santosh Shilimkar , Kevin Hilman , Balaji T K , Tony Lindgren , Jon Hunter Subject: Re: [PATCH v3] gpio: interrupt consistency check for OF GPIO IRQs References: <1377526030-32024-1-git-send-email-larsi@wh2.tu-dresden.de> <4094364.ACYUvMRRNa@lem-wkst-02> <52261C5C.9000102@wwwdotorg.org> <5034887.FlGzi4P5YS@lem-wkst-02> In-Reply-To: <5034887.FlGzi4P5YS@lem-wkst-02> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1801 Lines: 35 On 09/04/2013 03:21 AM, Lars Poeschel wrote: > On Wednesday 04 September 2013 11:29:00, Stephen Warren wrote: >> On 09/02/2013 03:38 AM, Lars Poeschel wrote: >>> Am Freitag, 30. August 2013, 13:53:45 schrieb Stephen Warren: >> ... >> >>>> Yet the current patch only addresses a limited set of cases, since it >>>> doesn't hook the APIs but rather parses the DT. It doesn't cover the >>>> non-DT case. It should if the feature is useful. >>> >>> As pointed out before, only DT has this problem, that, >> >> That's completely false. Both DT and non-DT can represent the exact same >> HW, and use the exact same drivers. It's equally possible to write a bug >> in a board file or a DT file (i.e. a typo or incorrect reading of the >> schematic) that causes the wrong GPIO or IRQ ID to be used, and hence >> for there to be conflicts. Any solution to this issue needs to address >> both cases. > > This is again not the point. This is not what this patch is trying to solve. > The patch is trying to solve problem A. But you are talking about problem B. > Sure I can write a bug in board files and I can write a bug in DT files. The > patch is not trying to prevent that. This is a completly different thing. I'm not trying to assert what this current patch was written to solve. I am asserting what the patch should be (have been) written to solve. My point is that we shouldn't only solve the problem in case B, but rather solve the problem in all cases (A, B, and anything else). Doing anything else isn't useful in my opinion; it's too special-cased. -- 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/