| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 11 Dec 2011 11:36:25 -0800 From: Tony Lindgren <tony@...mide.com> To: Linus Walleij <linus.walleij@...aro.org> Cc: Stephen Warren <swarren@...dia.com>, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-tegra@...r.kernel.org Subject: Re: [RFC 1/3] pinctrl: add a driver for NVIDIA Tegra * Linus Walleij <linus.walleij@...aro.org> [111209 15:17]: > On Fri, Dec 9, 2011 at 6:07 PM, Tony Lindgren <tony@...mide.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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists