| 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
| ||
|
Message-ID: <CACRpkdb4-0TfO-viUoZyW3VoLnVuo2ztHTX=8Hef3_RYWB52vg@mail.gmail.com> Date: Mon, 22 Aug 2011 14:28:12 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: Barry Song <21cnbao@...il.com> Cc: Linus Walleij <linus.walleij@...ricsson.com>, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, Grant Likely <grant.likely@...retlab.ca>, Stephen Warren <swarren@...dia.com>, Russell King <linux@....linux.org.uk>, Joe Perches <joe@...ches.com>, Linaro Dev <linaro-dev@...ts.linaro.org>, Lee Jones <lee.jones@...aro.org> Subject: Re: [PATCH 0/4 v4] pin controller subsystem v4 On Sun, Aug 21, 2011 at 4:42 PM, Barry Song <21cnbao@...il.com> wrote: > it seems there is not an actual example that gpio requests pin from > pinctrl yet. i might give one on SiRFprimaII. No good example yet, no. The reason is that for the U300 that I use as guinea pig, the GPIO driver is tangled up in discussions about how to handle the special control mechanics like requesting muxing and biasing pins. Right now it seems easier to rewrite all that to use the new pinctrl subsystem rather than actually trying to work it into the GPIO subsystem first and refactor from there, and that needs quite a bit of upfront work... Linus Walleij -- 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