linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: SAMSUNG: Add config option for number of additional GPIO pins.
Date: Tue, 12 Jan 2010 00:15:26 +0000	[thread overview]
Message-ID: <20100112001526.GH1224@trinity.fluff.org> (raw)
In-Reply-To: <20100111124927.GB27161@rakim.wolfsonmicro.main>

On Mon, Jan 11, 2010 at 12:49:27PM +0000, Mark Brown wrote:
> On Mon, Jan 11, 2010 at 12:27:15PM +0000, Ben Dooks wrote:
> 
> > Having this as a user settable field might be useful if plugging on
> > GPIO expanders at runtime.
> 
> If that gets to be anything other than an extremely niche use case the
> GPIO allocation would need to have a dynamic limit anyway, though.

Yes, however a kconfig case where you can set the minimum value of an
integer would make the whole extra-gpio configuration much cleaner and
avoid having toadd further configuration symbols when someone wants an
extra 256 or whatever GPIOS.

Having a dynamic GPIO range would also be nice, someone should look at
adding it to the GPIO code.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  reply	other threads:[~2010-01-12  0:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11  9:44 [PATCH 1/3] ARM: SAMSUNG: Add config option for number of additional GPIO pins Kukjin Kim
2010-01-11 10:33 ` Mark Brown
2010-01-11 12:27   ` Ben Dooks
2010-01-11 12:49     ` Mark Brown
2010-01-12  0:15       ` Ben Dooks [this message]
2010-01-12 15:25         ` Mark Brown
2010-01-12 20:46         ` [PATCH 1/3] ARM: SAMSUNG: Add config option for number ofadditional " H Hartley Sweeten

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=20100112001526.GH1224@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).