From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?C=c3=a9dric_Le_Goater?= Subject: Re: [PATCH] leds: pca955x: add GPIO support Date: Tue, 23 May 2017 12:58:42 +0200 Message-ID: <0df463c3-c08d-5f5d-0932-cba20ab870d5@kaod.org> References: <1494311772-21872-1-git-send-email-clg@kaod.org> <20b94199-a154-53cd-96d1-910ae3de1085@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-leds-owner@vger.kernel.org To: Linus Walleij , Jacek Anaszewski Cc: Richard Purdie , Pavel Machek , Rob Herring , Mark Rutland , "linux-leds@vger.kernel.org" , "devicetree@vger.kernel.org" , Joel Stanley List-Id: devicetree@vger.kernel.org On 05/23/2017 10:18 AM, Linus Walleij wrote: > On Thu, May 11, 2017 at 10:23 PM, Jacek Anaszewski > wrote: > >>> +Optional properties: >>> +- gpio-controller: allows pins to be used as GPIOs. > > Are these output-only? Then write something about that. no. input is also supported. >>> +- #gpio-cells: if present, must not be 0. > > Must be present and must be <2> > >>> +- gpio-base : base number of the pins used as GPIOs. If there are more >>> + than one, they should be contiguous. See 'type' property >>> + below. > > NACK. Not in my life. yes, indeed. this is useless. > Provide -1 in the Linux driver and use the ioctl() from userspace > to look up your gpios. Add .names array to the gpiochip if necessary, > define line names in the device tree for the board. > > Consult tools/gpio/* for the modern way of using GPIOs. OK. I wasn't aware of these. Thanks, C.