Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751084AbaLOV6g (ORCPT ); Mon, 15 Dec 2014 16:58:36 -0500 Received: from mout.kundenserver.de ([212.227.126.187]:57212 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750971AbaLOV6c (ORCPT ); Mon, 15 Dec 2014 16:58:32 -0500 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Ray Jui , Alexandre Courbot , Mark Rutland , "devicetree@vger.kernel.org" , Florian Fainelli , Russell King , Scott Branden , Pawel Moll , Ian Campbell , Linus Walleij , Christian Daudt , Linux Kernel Mailing List , Matt Porter , Joe Perches , Rob Herring , bcm-kernel-feedback-list@broadcom.com, "linux-gpio@vger.kernel.org" , Kumar Gala , Grant Likely Subject: Re: [PATCH v5 1/3] gpio: Cygnus: define Broadcom Cygnus GPIO binding Date: Mon, 15 Dec 2014 22:57:36 +0100 Message-ID: <2063145.N1Hk6vVF2S@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <548F5433.5090901@broadcom.com> References: <1418342706-14755-2-git-send-email-rjui@broadcom.com> <1628217.66frkAqHMc@wuerfel> <548F5433.5090901@broadcom.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:Gaj2zJD8ya7PT8TkA9jBDftqLzXz3E7JSlf3QOmBMxK8EBhkt6H lnGyHpeETkoCDzQ/r9CjWwK2rXGSVZzcXEXDKbVXNiu6wURT/i1kUN7J4AWDK7YRolBNiLn jtM6P/1OMv/SJ0slNM2Yvl5iQIaXSbyrBP+KXFx06aWFPzjDrM/YVqwgIO+99e/k1IF0YUp qTiP4i31H3MFZLzvmEx0g== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 15 December 2014 13:35:47 Ray Jui wrote: > > Like I said previously, dynamic GPIO allocation works fine in the > kernel, as long as all of our GPIO clients in the kernel use gpiod based > API, which is what we will enforce going forward. The only problem is > with some of our customers who use GPIO through sysfs and expect fixed > global GPIO numbers. Thinking about this more, it's probably not that > difficult to add a script for those customers to convert/map the GPIO > numbers based on readings parsed from sysfs, so I guess that's fine. > I think we discussed the user space interface a number of times in the past, but I forgot the outcome. Either there is already a way to name gpio lines uniquely in sysfs, or there should be one. Can you reach the gpio interfaces using /sys/devices/0001234.bus/1234566.gpiocontroller/...? Arnd -- 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/