Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751868AbbHTHFN (ORCPT ); Thu, 20 Aug 2015 03:05:13 -0400 Received: from metis.ext.pengutronix.de ([92.198.50.35]:53001 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751090AbbHTHFM (ORCPT ); Thu, 20 Aug 2015 03:05:12 -0400 Date: Thu, 20 Aug 2015 09:05:07 +0200 From: Sascha Hauer To: linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linus.walleij@linaro.org, nicolas.ferre@atmel.com Subject: Re: [RFC PATCH 0/3] New Atmel PIO4 pinctrl/gpio driver Message-ID: <20150820070507.GS5161@pengutronix.de> References: <1438355290-28255-1-git-send-email-ludovic.desroches@atmel.com> <20150805073117.GP5161@pengutronix.de> <20150810065334.GC2635@odux.rfo.atmel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150810065334.GC2635@odux.rfo.atmel.com> X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-IRC: #ptxdist @freenode X-Accept-Language: de,en X-Accept-Content-Type: text/plain X-Uptime: 08:39:51 up 56 days, 1:01, 108 users, load average: 0.03, 0.13, 0.14 User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c0 X-SA-Exim-Mail-From: sha@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2064 Lines: 54 On Mon, Aug 10, 2015 at 08:53:34AM +0200, Ludovic Desroches wrote: > Hi Sascha, > > On Wed, Aug 05, 2015 at 09:31:17AM +0200, Sascha Hauer wrote: > > On Fri, Jul 31, 2015 at 05:08:07PM +0200, Ludovic Desroches wrote: > > > Hi, > > > > > > Following our discussion, I send an RFC version of my driver. RFC because it is > > > not totally achieved, some cleanup and feature addition is needed. > > > > > > At least, we could discuss about the 'core' part. I have used the pinmux > > > property as Mediatek driver. Patch 3 is the internal dt files we are using. > > > > As you can imagine I am fine with the binding, so I can add my acked-by > > once you send a non-RFC version. > > > > Great, I'm glad to hear that. > > > The only thing I never understood is what's so special about GPIOs that > > they have to bypass the pinctrl framework and instead a gpio_request > > magically translates a gpio into a pin. > > Not sure to really understand your concern here... Do you mean I could > get rid of gpio_request_enable()? I would expect a gpio to be a pin like every other pin, hence configured via the pinctrl framework and not implicitly via gpio_request(). > > > Wouldn't it make sense to at > > least add the pins in their GPIO mode to > > arch/arm/boot/dts/sama5d2-pinfunc.h? > > It is done, PIN_PA0 could be used for this purpose. I would expect a define like: #define PIN_PA3__GPIO PINMUX_PIN(PIN_PA3, 0, 2) PIN_PAx only contains the pin number, but not the function. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- 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/