From: Arnd Bergmann <arnd@arndb.de>
To: Daniel Mack <zonque@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>,
Linus Walleij <linus.walleij@stericsson.com>
Subject: Re: [PATCH] gpiolib: fix chip->base handling in of_gpio_simple_xlate()
Date: Tue, 24 Jul 2012 12:56:56 +0000 [thread overview]
Message-ID: <201207241256.56535.arnd@arndb.de> (raw)
In-Reply-To: <500D632B.3000206@gmail.com>
On Monday 23 July 2012, Daniel Mack wrote:
> (Cc: Arnd)
>
> On 22.07.2012 19:10, Daniel Mack wrote:
> > of_gpio_simple_xlate() is called for each chip when a GPIO is looked up.
> > When registering several chips off the same DT node (with different pin
> > offsets) however, the lookup fails as the GPIO number passed in to
> > of_gpio_simple_xlate() is likely higher than the chip's ->ngpio value.
> >
> > Fix that by taking into account the chip's ->base value, and return the
> > relative offset of the pin inside the chip.
> >
> > Signed-off-by: Daniel Mack <zonque@gmail.com>
> > Cc: Grant Likely <grant.likely@secretlab.ca>
> > Cc: Linus Walleij <linus.walleij@stericsson.com>
> > ---
> >
> > I'm currently porting the PXA pieces over to DT, and stumbled over what
> > looks like an obvious bug to me. Correct me if I'm mistaken, but I see
> > no reason why one shouldn't be able to instanciate several GPIO chips
> > from a single DT node.
But why would you do that? Both the "gpiochip" and its DT representation
attempt to represent the hardware structure. If they don't match, then
I'd assume one of them is wrong ;-)
> > diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c
> > index d18068a..51bc232 100644
> > --- a/drivers/gpio/gpiolib-of.c
> > +++ b/drivers/gpio/gpiolib-of.c
> > @@ -147,13 +147,13 @@ int of_gpio_simple_xlate(struct gpio_chip *gc,
> > if (WARN_ON(gpiospec->args_count < gc->of_gpio_n_cells))
> > return -EINVAL;
> >
> > - if (gpiospec->args[0] >= gc->ngpio)
> > + if (gpiospec->args[0] >= gc->ngpio + gc->base)
> > return -EINVAL;
> >
> > if (flags)
> > *flags = gpiospec->args[1];
> >
> > - return gpiospec->args[0];
> > + return gpiospec->args[0] - gc->base;
> > }
> > EXPORT_SYMBOL(of_gpio_simple_xlate);
Where would that gc->base come from?
Arnd
next prev parent reply other threads:[~2012-07-24 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 17:10 [PATCH] gpiolib: fix chip->base handling in of_gpio_simple_xlate() Daniel Mack
2012-07-23 14:43 ` Daniel Mack
2012-07-24 12:56 ` Arnd Bergmann [this message]
2012-07-24 13:04 ` Daniel Mack
2012-07-24 14:08 ` Arnd Bergmann
2012-07-24 15:22 ` Daniel Mack
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=201207241256.56535.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zonque@gmail.com \
/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).