From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751367AbdAaJm2 (ORCPT ); Tue, 31 Jan 2017 04:42:28 -0500 Received: from mail-it0-f52.google.com ([209.85.214.52]:36818 "EHLO mail-it0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751189AbdAaJmK (ORCPT ); Tue, 31 Jan 2017 04:42:10 -0500 MIME-Version: 1.0 In-Reply-To: <20170130171604.11266-1-vilhelm.gray@gmail.com> References: <20170130171604.11266-1-vilhelm.gray@gmail.com> From: Linus Walleij Date: Tue, 31 Jan 2017 10:41:35 +0100 Message-ID: Subject: Re: [PATCH] iio: stx104: Add support for GPIO names To: William Breathitt Gray Cc: Jonathan Cameron , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald , "linux-iio@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 30, 2017 at 6:16 PM, William Breathitt Gray wrote: > This patch sets the gpio_chip names option with an array of GPIO line > names that match the manual documentation for the Apex Embedded Systems > STX104. This should make it easier for users to identify which GPIO line > corresponds to a respective GPIO pin on the device. > > Signed-off-by: William Breathitt Gray (...) > +#define STX104_NGPIO 8 > +static const char *stx104_names[STX104_NGPIO] = { > + "DIN0", "DIN1", "DIN2", "DIN3", "DOUT0", "DOUT1", "DOUT2", "DOUT3" > +}; (...) > + stx104gpio->chip.ngpio = STX104_NGPIO; > + stx104gpio->chip.names = stx104_names; If the device has a gpio-controller tagged node in a device tree, it is better to use gpio-line-names = "foo" ...; for this. For ACPI there is something similar. If it is spawn from this device without any GPIO child node or hardware description outside of the kernel driver, such as ISA/PCI or whatever, this is a good way. This is an isa_driver and falls in the latter category, so: Reviewed-by: Linus Walleij Yours, Linus Walleij