DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=pacbell.net;
  h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id;
  b=JkCdqEwddBt/o1UiUFlIFzsYxKwmHegkdzg1AB9SlDiNojEyqUrZAVNRdf5jvUKV6UWBGCDUw67DES3qHeGKas7Qr2NGNVgUGlLFOhQdNbelriRUnjUhVv6jFaj7np39/cJi0pLzYAthU4L6ybcdcFj2WBzpQ3ndrquIVEbIQi4=  ;
From: David Brownell <david-b@pacbell.net>
To: Anton Vorontsov <avorontsov@ru.mvista.com>
Subject: Re: [PATCH] gpiolib: implement dynamic base allocation
Date: Wed, 5 Mar 2008 15:40:57 -0800
User-Agent: KMail/1.9.6
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
References: <20080304170307.GA29979@localhost.localdomain> <20080305152450.167c9e8c.akpm@linux-foundation.org>
In-Reply-To: <20080305152450.167c9e8c.akpm@linux-foundation.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200803051540.57499.david-b@pacbell.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1606
Lines: 38

On Wednesday 05 March 2008, Andrew Morton wrote:
> On Tue, 4 Mar 2008 20:03:07 +0300
> Anton Vorontsov <avorontsov@ru.mvista.com> wrote:
> 
> > If gpio_chip->base is negative during registration, gpiolib requests
> > dynamic base allocation. This is useful for devices being registered
> > at run-time (in contrast to platform devices).
> > 
> > Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
> > ---
> >  drivers/gpio/gpiolib.c |   42 ++++++++++++++++++++++++++++++++++++------
> >  1 files changed, 36 insertions(+), 6 deletions(-)
> > 
> 
> This conflicts in non-trivial ways with gpio-define-gpio_is_valid.patch. 
> Could you please redo and retest against 2.6.25-rc3-mm1?

And when you do that, could you make it assign GPIO numbers from
the biggest number on down, instead of from the smallest on up?

Platforms normally assign those numbers from the bottom up ... so
dynamic assignment should try to avoid reusing any numbers that may
have been explicitly assigned, but not yet registered.  (Of course,
if you can come up with a cleaner solution than that, it'd be great.
Maybe platforms should also be able to mark ranges as "in use" as
they start up, or something.)

And please add a pr_debug level message reporting dynamically
assigned ranges.  That way, when problems crop up it'll be that
much easier to notice what went wrong.

- Dave

--
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/