devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Arnd Bergmann <arnd@arndb.de>, Roland Stigge <stigge@antcom.de>
Cc: arm@kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linus.walleij@stericsson.com, kevin.wells@nxp.com,
	srinivas.bakki@nxp.com, devicetree-discuss@lists.ozlabs.org,
	rob.herring@calxeda.com
Subject: Re: [PATCH RESEND v8] gpio: Device tree support for LPC32xx
Date: Fri, 11 May 2012 11:32:57 -0600	[thread overview]
Message-ID: <20120511173257.98E2C3E0791@localhost> (raw)
In-Reply-To: <201205111322.15191.arnd@arndb.de>

On Fri, 11 May 2012 13:22:14 +0000, Arnd Bergmann <arnd@arndb.de> wrote:
> On Friday 11 May 2012, Roland Stigge wrote:
> > Right. Personally, I would be fine with either of my v8 (all banks in
> > dt, referenced naturally by name) and v9 (one simple DT entry for the
> > whole GPIO controller, integer index for referencing banks) patches.
> > 
> > Consider the DT-documented mapping in the latter case:
> > 
> >       0: GPIO P0
> >       1: GPIO P1
> >       2: GPIO P2
> >       3: GPIO P3
> >       4: GPI P3
> >       5: GPO P3
> > 
> > Not too difficult and would also be acceptable, IMO.
> > 
> > So Arnd and Grant, please agree one of those and pick it. :-)
> > 
> 
> Grant is maintainer for both GPIO and DT, so his opinion is what
> counts in this case.
> I was merely giving the background on how we got there so he
> can make an informed decision.

It adds a lot of boilerplate to the DT to split it up into nodes and
mapping index to a bank isn't onerous.  I think I like the single node
with #gpio-cells = <3> better.  When DTC handles named constants then
it will be even easier.

Just need to decide on the best way to implement it.  Arnd, can you
review Roland's v9 patches for me and give me your opinion?

g.

      reply	other threads:[~2012-05-11 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 19:57 [PATCH RESEND v8] gpio: Device tree support for LPC32xx Roland Stigge
     [not found] ` <1336679838-30738-1-git-send-email-stigge-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org>
2012-05-10 23:41   ` Grant Likely
2012-05-11 12:19     ` Arnd Bergmann
2012-05-11 12:47       ` Roland Stigge
2012-05-11 13:22         ` Arnd Bergmann
2012-05-11 17:32           ` Grant Likely [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120511173257.98E2C3E0791@localhost \
    --to=grant.likely@secretlab.ca \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=kevin.wells@nxp.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=srinivas.bakki@nxp.com \
    --cc=stigge@antcom.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).