| 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: Tue, 10 Jan 2012 21:05:15 +0800 From: Shawn Guo <shawn.guo@...aro.org> To: Dong Aisheng-B29396 <B29396@...escale.com> Cc: Stephen Warren <swarren@...dia.com>, Dong Aisheng <dongas86@...il.com>, "linus.walleij@...ricsson.com" <linus.walleij@...ricsson.com>, "s.hauer@...gutronix.de" <s.hauer@...gutronix.de>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "rob.herring@...xeda.com" <rob.herring@...xeda.com>, "kernel@...gutronix.de" <kernel@...gutronix.de>, "cjb@...top.org" <cjb@...top.org>, "devicetree-discuss@...ts.ozlabs.org" <devicetree-discuss@...ts.ozlabs.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: [RFC PATCH v3 2/5] pinctrl: add dt binding support for pinmux mappings On Tue, Jan 10, 2012 at 08:21:05AM +0000, Dong Aisheng-B29396 wrote: > Here what I wonder is that do we need to allow the platform to use a func-name > property in their pinmux func node or pinmux group node to specify the name. I do not see the necessity. > If it is allowed, then it could be flexible for soc to define their names. > If not there may be limitations on their node names since we can only get it from > the node name. To me, the node name is perfectly fine to be used for that purpose. -- Regards, Shawn -- 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