lkml.org 
[lkml]   [2013]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH 1/9] gpiolib: link all gpio_chips using a list
Date
On Tue, 5 Feb 2013 18:00:56 +0100, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Sat, Feb 2, 2013 at 5:29 PM, Alexandre Courbot <acourbot@nvidia.com> wrote:
>
> > Add a list member to gpio_chip that allows all chips to be parsed
> > quickly. The current method requires parsing the entire GPIO integer
> > space, which is painfully slow. Using a list makes many chip operations
> > that involve lookup or parsing faster, and also simplifies the code. It
> > is also necessary to eventually get rid of the global gpio_desc[] array.
> >
> > The list of gpio_chips is always ordered by base GPIO number to ensure
> > chips traversal is done in the right order.
> >
> > Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
>
> OK!
>
> > + * Return -EBUSY if the new chip overlaps with some other chip's integer
> > + * space.
> (...)
> > + /* are we stepping on the chip right before? */
> > + if (pos != &gpio_chips && pos->prev != &gpio_chips) {
> > + _chip = list_entry(pos->prev, struct gpio_chip, list);
> > + if (_chip->base + _chip->ngpio > chip->base) {
> > + dev_err(chip->dev,
> > + "GPIO integer space overlap, cannot add chip\n");
> > + err = -EBUSY;
> > + }
> > + }
>
> This robustness change on its own is a merit for merging the patch.
> And keeping a list of gpiochips available is great for stuff like
> debugfs.
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Applied, thanks.

g.



\
 
 \ /
  Last update: 2013-02-09 11:41    [W:0.132 / U:1.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site