All of lore.kernel.org
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] SPEAr pinctrl updates for v-3.5
Date: Wed, 20 Jun 2012 10:25:30 +0200	[thread overview]
Message-ID: <CACRpkday9+zhMHWWjNNBfhhQ2NXPc+RoGkHvxodud5HY7hLm4g@mail.gmail.com> (raw)
In-Reply-To: <CAOh2x=kOU=X2V5zBg4G_SWzNSfQyoeygwgW-vO-xxRkDXzZDJQ@mail.gmail.com>

On Tue, Jun 19, 2012 at 4:11 PM, viresh kumar <viresh.linux@gmail.com> wrote:

> @Grant: Can we have your comments here please. Or any other better
> solution to the problem
> we are facing. I do hope, my last suggestion is not that bad.

I did hunt Grant down in Hong Kong (this make me sound like some
secret agent...) and we discussed this with Dong Aisheng.

The outcome was basically this work item from Linaro:
https://blueprints.launchpad.net/linux-linaro/+spec/pinctrl-gpiorange-makeover

So the idea is that GPIO drivers should register their pin ranges
instead of the other way around (pinctrl drivers register them, as it
is done today), and that we need to move the mapping to be
GPIO-driver local, which in turn mandates stashing the
struct gpio_chip into the GPIO range mapping.

Not a simple refactoring but probably necessary (all current users need
to be switched over).

Interested? ;-)

Yours,
Linus Walleij

  reply	other threads:[~2012-06-20  8:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 11:15 [GIT PULL] SPEAr pinctrl updates for v-3.5 Viresh Kumar
2012-05-10 11:33 ` viresh kumar
2012-05-12 21:42   ` Arnd Bergmann
2012-05-12 23:54     ` Linus Walleij
2012-05-14  4:02       ` Viresh Kumar
2012-05-17  4:26       ` Viresh Kumar
2012-05-20 20:45         ` Linus Walleij
2012-06-19 14:11           ` viresh kumar
2012-06-20  8:25             ` Linus Walleij [this message]
2012-09-01 11:22               ` shiraz hashim
2012-09-03 11:48                 ` Linus Walleij
2012-09-04  4:19                   ` Shiraz Hashim
2012-09-04  7:17                     ` Linus Walleij
2012-10-27  9:33                   ` viresh kumar

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=CACRpkday9+zhMHWWjNNBfhhQ2NXPc+RoGkHvxodud5HY7hLm4g@mail.gmail.com \
    --to=linus.walleij@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.