| 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: <CACRpkdagdO3_6DmKYaCwmx4Jju=E_uy86_QqdKLA3+VK7JNPjg@mail.gmail.com> Date: Thu, 10 Jan 2013 11:49:20 +0100 From: Linus Walleij <linus.walleij@...aro.org> To: Tony Prisk <linux@...sktech.co.nz> Cc: Grant Likely <grant.likely@...retlab.ca>, Linus Walleij <linux.walleij@...aro.org>, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, vt8500-wm8505-linux-kernel@...glegroups.com Subject: Re: [PATCH] gpio: vt8500: Export dedicated GPIO before multifunction pins. On Sun, Dec 30, 2012 at 9:29 PM, Tony Prisk <linux@...sktech.co.nz> wrote: > The vendor does not provide numbering for gpio pins. Vendor source > exports dedicated gpio pins first, followed by multifunction pins. > As this is what end users expect, this patch changes vt8500 and wm8505 > to do the same. > > Signed-off-by: Tony Prisk <linux@...sktech.co.nz> So how many existing userspace applications does this patch break? Has this system been widely deployed so a kernel upgrade will cause problems for people? But applied anyway, unless someone screams about it real soon now. That seems to be the only way to get people to tell us about their use cases. Could you consider adding names to the exported GPIO pins on the vt8500 series please? Then userspace can atleast try to locate the right pin. 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