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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 10 Jan 2013 11:49:20 +0100
From:	Linus Walleij <>
To:	Tony Prisk <>
Cc:	Grant Likely <>,
	Linus Walleij <>,,,
Subject: Re: [PATCH] gpio: vt8500: Export dedicated GPIO before multifunction pins.

On Sun, Dec 30, 2012 at 9:29 PM, Tony Prisk <> 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 <>

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.

Linus Walleij
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists