linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/3] pinctrl: add a driver for NVIDIA Tegra
Date: Sun, 11 Dec 2011 11:36:25 -0800	[thread overview]
Message-ID: <20111211193625.GE31337@atomide.com> (raw)
In-Reply-To: <CACRpkdaco=967cKHUcj9VNKc_HyT7Mw30Z9HVdfgsUsHbps8bQ@mail.gmail.com>

* Linus Walleij <linus.walleij@linaro.org> [111209 15:17]:
> On Fri, Dec 9, 2011 at 6:07 PM, Tony Lindgren <tony@atomide.com> wrote:
> 
> > - We currently have hard time supporting pin groups with pins
> > ?coming from multiple pinmux driver instances
> 
> Pin groups are per definiton per-controller inctance. That is a
> given side effect of not having a global pin space.
> 
> But you can create two groups of the same name on two
> pin controllers so that e.g. pinctrl.0 and pinctrl.1 have
> a group named "foo", then map both to a certain device
> in the board pinmux map.
> 
> You will have to request them individually however, like
> with two hogs or two pinmux_get() calls specifying the
> name of each map, else you will just get the first one.
> 
> Not that I've tried it, but that's how it's supposed to work...

Yes a little bit of trickery is needed there, I'll look into
it more as we already have two controller instances on omap4.

Regards,

Tony

  reply	other threads:[~2011-12-11 19:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 22:13 [RFC 0/3] pinctrl: add a driver for NVIDIA Tegra Stephen Warren
     [not found] ` <1323382390-14892-2-git-send-email-swarren@nvidia.com>
2011-12-09 14:01   ` [RFC 1/3] " Linus Walleij
2011-12-09 17:07     ` Tony Lindgren
2011-12-09 23:49       ` Linus Walleij
2011-12-11 19:36         ` Tony Lindgren [this message]
2011-12-09 17:28     ` Stephen Warren
2011-12-09 18:00       ` Tony Lindgren
2011-12-09 23:55       ` Linus Walleij
2011-12-12 18:06         ` Stephen Warren
2011-12-13  0:27           ` Linus Walleij

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=20111211193625.GE31337@atomide.com \
    --to=tony@atomide.com \
    --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).