Re: [RFC PATCH 0/3] New Atmel PIO4 pinctrl/gpio driver
From: Ludovic Desroches
Date: Mon Aug 10 2015 - 02:54:00 EST
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()?
> Wouldn't it make sense to at
> least add the pins in their GPIO mode to
It is done, PIN_PA0 could be used for this purpose.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/