| 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: <CACRpkdb4w26vuOtR1bAhQ6k=1uQx=np4WwoabvH8pOq8HK54=w@mail.gmail.com> Date: Mon, 23 Dec 2013 18:26:49 +0100 From: Linus Walleij <linus.walleij@...aro.org> To: Pawel Moll <pawel.moll@....com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Samuel Ortiz <sameo@...ux.intel.com>, Arnd Bergmann <arnd@...db.de>, Jon Medhurst <tixy@...aro.org>, "arm@...nel.org" <arm@...nel.org>, Olof Johansson <olof@...om.net>, Alexandre Courbot <gnurou@...il.com>, Anton Vorontsov <anton@...msg.org> Subject: Re: [RFC 03/18] GPIO: gpio-generic: Add label to platform data On Mon, Dec 23, 2013 at 5:23 PM, Pawel Moll <pawel.moll@....com> wrote: > When registering more than one platform device, it is > useful to set the gpio chip label in the platform data. > > Signed-off-by: Pawel Moll <pawel.moll@....com> > Cc: Linus Walleij <linus.walleij@...aro.org> > Cc: Alexandre Courbot <gnurou@...il.com> > Cc: Anton Vorontsov <anton@...msg.org> Good point. But what about also adding device tree support for naming the chips while you're at it? I imagine a generic gpiochip property in Documentation/devicetree/bindings/gpio/gpio.txt Yours, 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