From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756852AbaAHP5X (ORCPT ); Wed, 8 Jan 2014 10:57:23 -0500 Received: from fw-tnat.austin.arm.com ([217.140.110.23]:58884 "EHLO collaborate-mta1.arm.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755363AbaAHP5U (ORCPT ); Wed, 8 Jan 2014 10:57:20 -0500 Message-ID: <1389196639.23721.16.camel@hornet> Subject: Re: [RFC 03/18] GPIO: gpio-generic: Add label to platform data From: Pawel Moll To: Linus Walleij Cc: "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Samuel Ortiz , Arnd Bergmann , Jon Medhurst , "arm@kernel.org" , Olof Johansson , Alexandre Courbot , Anton Vorontsov Date: Wed, 08 Jan 2014 15:57:19 +0000 In-Reply-To: References: <1387815830-8794-1-git-send-email-pawel.moll@arm.com> <1387815830-8794-4-git-send-email-pawel.moll@arm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Greetings (and the usual: Happy New Year!) On Mon, 2013-12-23 at 17:26 +0000, Linus Walleij wrote: > On Mon, Dec 23, 2013 at 5:23 PM, Pawel Moll wrote: > > > When registering more than one platform device, it is > > useful to set the gpio chip label in the platform data. > > > > Signed-off-by: Pawel Moll > > Cc: Linus Walleij > > Cc: Alexandre Courbot > > Cc: Anton Vorontsov > > Good point. But what about also adding device tree support for > naming the chips while you're at it? > > I imagine a generic gpiochip property in > Documentation/devicetree/bindings/gpio/gpio.txt Well, this has been discussed almost to death already (as you may remember ;-) in the thread: http://www.spinics.net/lists/devicetree/msg00072.html (only portions survived) Although I was in favour of the generic binding (as were you if I remember correctly), the final non-conclusion was not to open the "generic door". Fair enough with me, I went the defined-in-code way here... Paweł