Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 2, 2012 at 10:19 AM, Koen Kooi <koen@xxxxxxxxxxxxxxxxxxxxx> 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-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux