From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Cochran Subject: Re: [PATCH 1/2] gpio: dwapb: Use human understandable gpio numbering. Date: Thu, 2 Jul 2015 16:26:01 +0200 Message-ID: <20150702142601.GB9349@localhost.localdomain> References: <5594E9F6.7040701@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <5594E9F6.7040701@linutronix.de> Sender: linux-gpio-owner@vger.kernel.org To: Sebastian Andrzej Siewior Cc: linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, Alan Tull , Alexandre Courbot , Dinh Nguyen , Linus Walleij List-Id: devicetree@vger.kernel.org On Thu, Jul 02, 2015 at 09:36:22AM +0200, Sebastian Andrzej Siewior wrote: > If you are in a specific SoC you could do > base = of_alias_get_id(np, "gpio") * num_of_gpio_per_chip > and get consistent numbers / sane. And what about /sys/class/gpio ? > I think this is the one reason why there is no generic binding for the > starting address. The other reason might be that this is simply a user > space problem. To get consistent numbers all you need to do to lookup > each gpio's memory address and decide if this is the one you look for. The user should be able to simply look up a GPIO in the data sheet, and then use it from a shell script. Why not make that easy to do? (Other gpio controllers are doing that, too, BTW.) Thanks, Richard