On Tue, May 30, 2017 at 6:40 PM, Dmitry Torokhov
[off-list ref] wrote:
On Tue, May 30, 2017 at 02:09:18PM +0200, Linus Walleij wrote:
quoted
+ /*
+ * This key appears in the vendor driver, but I have
+ * not been able to provoke it.
+ */
+ tk->codes[6] = KEY_O;
If there is no way to make the device produce this key, should we mark
is as KEY_RESERVED? KEY_O would not be suitable in any case, we'd need
to find more suitable keycode for whatever function is has.
OK I'm in on this.
If it is OK I can make the change locally.
Sure go ahead when applying!
Yours,
Linus Walleij