Skip to content

K
Kernel

openeuler / Kernel
接近 2 年 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 29 5月, 2014 4 次提交
  3. 15 5月, 2014 9 次提交
  5. 14 5月, 2014 1 次提交
    • C
      Input: pxa27x-keypad - fix generating scancode · c5ec1948
      由 Chao Xie 提交于 
      The number of columns of pxa27x-keypad used by various boards is not fixed.
When building keymap with call to:

matrix_keypad_build_keymap(keymap_data, NULL,
                           pdata->matrix_key_rows,
                           pdata->matrix_key_cols,
                           keypad->keycodes, input_dev);

it will internally calculate needed row shift and use it to fill the
keymap. Therefore when calculating the "scancode" we should no longer use
constant row shift but also calculate it from number of columns.
Signed-off-by: NChao Xie <chao.xie@marvell.com>
Signed-off-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>
      c5ec1948
  7. 13 5月, 2014 1 次提交
    • A
      Input: fix ps2/serio module dependency · 0a4ac2ea
      由 Arnd Bergmann 提交于 
      The ps2 mouse and keyboard drivers use the "serio" framework that they
correctly select in Kconfig, and that in turn depends on the i8042 driver,
which is also allowed to be disabled for architectures that don't have an
i8042.

However, Kconfig also allows i8042 to be built as a module while
the serio framework is built-in, which causes this link error:

drivers/built-in.o: In function `ps2_begin_command':
:(.text+0x26b6cc): undefined reference to `i8042_check_port_owner'
:(.text+0x26b6d4): undefined reference to `i8042_lock_chip'
drivers/built-in.o: In function `ps2_end_command':
:(.text+0x26b734): undefined reference to `i8042_check_port_owner'
:(.text+0x26b73c): undefined reference to `i8042_unlock_chip'

On x86, a specific 'select SERIO_I8042' takes care of it, but
not on the other architecture that potentially have a i8042.

This patch changes the Kconfig logic to ensure that whenever
there is an i8042, it does get used for the serio driver, avoiding
the link error above.
Signed-off-by: NArnd Bergmann <arnd@arndb.de>
Signed-off-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>
      0a4ac2ea
  9. 25 4月, 2014 2 次提交
  11. 31 3月, 2014 5 次提交
  13. 28 3月, 2014 1 次提交
  15. 18 2月, 2014 1 次提交
  17. 16 2月, 2014 1 次提交
  19. 07 1月, 2014 2 次提交
  21. 04 1月, 2014 1 次提交
  23. 01 1月, 2014 1 次提交
    • D
      Input: cros_ec_keyb - fix problems with backslash · 64757eba
      由 Doug Anderson 提交于 
      The driver can't deal with two entries its keymap having the same keycode.
When this happens it will get confused about whether the key is down or up
and will cause some screwy behavior.

We need to have two entries for KEY_BACKSLASH to handle US and UK
keyboards. Specifically:
* On the US keyboard the backslash key (above enter) is r3 c11 and is
  supposed to be reported as BACKSLASH.
* On the UK keyboard the # key (left of enter) is r4 c10 and is
  supposed to be reported as BACKSLASH.
* On the UK keyboard the \ key (left of Z) is r2 c7 and is supposed to
  be reported as KEY_102ND.

Note that both keyboards (US and UK) have only one physical backslash
key so the constraint that each physical key should have its own keycode
still stands.
Signed-off-by: NDoug Anderson <dianders@chromium.org>
Signed-off-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>
      64757eba
  25. 12 12月, 2013 1 次提交
  27. 07 12月, 2013 1 次提交
  29. 06 12月, 2013 2 次提交
  31. 26 11月, 2013 1 次提交
  33. 11 11月, 2013 1 次提交
  35. 31 10月, 2013 2 次提交
  37. 16 10月, 2013 1 次提交
  39. 06 10月, 2013 2 次提交