[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130728122055.GO9858@sirena.org.uk>
Date: Sun, 28 Jul 2013 13:20:55 +0100
From: Mark Brown <broonie@...nel.org>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: "grant.likely@...aro.org" <grant.likely@...aro.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"rob@...dley.net" <rob@...dley.net>,
"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
"lee.jones@...aro.org" <lee.jones@...aro.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"gg@...mlogic.co.uk" <gg@...mlogic.co.uk>,
"kishon@...com" <kishon@...com>,
Stephen Warren <swarren@...dia.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 2/2] pinctrl: palmas: add pincontrol driver
On Sat, Jul 27, 2013 at 03:53:27PM +0530, Laxman Dewangan wrote:
> On Friday 26 July 2013 10:11 PM, Mark Brown wrote:
> >>+ gpio4_sysen1, gpio5_clk32kgaudio_usb_psel, gpio6_sysen2,
> >Would it not be easier to just name the GPIOs gpioN rather than using
> >the full names with the possible functions?
> I took the name approach as what we have on Tegra.
> But I think I can put the name of the pins same as what we have in
> datasheet. So pin name will be exact same as what we have in
> datasheet. That will be easy to interpret.
I was thinking more about ease of typing than ease of understanding
here!
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists