Messages in this thread | | | From | Grant Likely <> | Date | Mon, 5 Nov 2012 00:32:48 +0000 | Subject | Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2 |
| |
On Fri, Nov 2, 2012 at 10:19 AM, Koen Kooi <koen@dominion.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.
| |