From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755256AbdDGK4n (ORCPT ); Fri, 7 Apr 2017 06:56:43 -0400 Received: from mail-wr0-f172.google.com ([209.85.128.172]:36418 "EHLO mail-wr0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754029AbdDGK4e (ORCPT ); Fri, 7 Apr 2017 06:56:34 -0400 Date: Fri, 7 Apr 2017 11:56:29 +0100 From: Lee Jones To: Linus Walleij Cc: Paul Cercueil , Alexandre Courbot , Rob Herring , Mark Rutland , Ralf Baechle , Boris Brezillon , Thierry Reding , Bartlomiej Zolnierkiewicz , Maarten ter Huurne , Lars-Peter Clausen , Paul Burton , James Hogan , "linux-gpio@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Linux MIPS , "linux-mmc@vger.kernel.org" , "linux-mtd@lists.infradead.org" , "linux-pwm@vger.kernel.org" , "linux-fbdev@vger.kernel.org" Subject: Re: [PATCH v4 03/14] pinctrl-ingenic: add a pinctrl driver for the Ingenic jz47xx SoCs Message-ID: <20170407105629.n6a2cxt3pof66gu2@dell> References: <20170125185207.23902-2-paul@crapouillou.net> <20170402204244.14216-1-paul@crapouillou.net> <20170402204244.14216-4-paul@crapouillou.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.2-neo (2016-08-21) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 07 Apr 2017, Linus Walleij wrote: > On Sun, Apr 2, 2017 at 10:42 PM, Paul Cercueil wrote: > > > This driver handles pin configuration and pin muxing for the > > JZ4740 and JZ4780 SoCs from Ingenic. > > > > Signed-off-by: Paul Cercueil > (...) > > + select MFD_CORE > (...) > > +#include > > That's unorthodox. Still quite pretty! > I would nee Lee Jones to say something about this, as it is > essentially hijacking MFD into the pinctrl subsystem. > > > +static struct mfd_cell ingenic_pinctrl_mfd_cells[] = { > > + { > > + .id = 0, > > + .name = "GPIOA", > > + .of_compatible = "ingenic,gpio-bank-a", > > + }, > > + { > > + .id = 1, > > + .name = "GPIOB", > > + .of_compatible = "ingenic,gpio-bank-b", > > + }, > > + { > > + .id = 2, > > + .name = "GPIOC", > > + .of_compatible = "ingenic,gpio-bank-c", > > + }, > > + { > > + .id = 3, > > + .name = "GPIOD", > > + .of_compatible = "ingenic,gpio-bank-d", > > + }, > > + { > > + .id = 4, > > + .name = "GPIOE", > > + .of_compatible = "ingenic,gpio-bank-e", > > + }, > > + { > > + .id = 5, > > + .name = "GPIOF", > > + .of_compatible = "ingenic,gpio-bank-f", > > + }, > > +}; > (...) > > + err = devm_mfd_add_devices(dev, 0, ingenic_pinctrl_mfd_cells, > > + ARRAY_SIZE(ingenic_pinctrl_mfd_cells), NULL, 0, NULL); > > + if (err) { > > + dev_err(dev, "Failed to add MFD devices\n"); > > + return err; > > + } > > I guess the alternative would be to reimplement the MFD structure. > > Did you check the approach to use "simple-mfd" and just let the subnodes > spawn as devices that way? I guess you did and this adds something > necessary. I'd like to hear what the OP has to say about why this is necessary. However, as a first glimpse, I'm dead against exporting MFD functionality to outside of the subsystem. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog