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: Mon, 5 Nov 2012 00:32:48 +0000 From: Grant Likely <grant.likely@...retlab.ca> To: Koen Kooi <koen@...inion.thruhere.net> Cc: "Cousson, Benoit" <b-cousson@...com>, Jason Kridner <jkridner@...gleboard.org>, Tony Lindgren <tony@...mide.com>, paul@...an.com, linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org, "Porter, Matt" <mporter@...com>, Russ Dill <russ.dill@...il.com>, khilman@...com Subject: Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2 On Fri, Nov 2, 2012 at 10:19 AM, Koen Kooi <koen@...inion.thruhere.net> wrote: > button@1 { > debounce_interval = <50>; > linux,code = <105>; > label = "left"; > gpios = <&gpio2 16 0x0>; > gpio-key,wakeup; > autorepeat; > }; > > Is the "linux,code" pure hardware or have there already been exceptions to that rule? I generally push back on "linux,blah" bindings since they have the tendency to change over time when someone changes the driver. However, since the keycodes are part of the Linux userspace ABI, and are therefore pretty much set it stone, I didn't object to the linux,keycode binding. There are already drivers using it. g. -- 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