| 9745ade2 | 27-Oct-2017 |
Joseph Chen <chenjh@rock-chips.com> |
input: rk8xx pwrkey: add some optimization
1. add key name and type;
2. clear both fall and rise interrupt when detect rise.
Change-Id: I0698f3decc4b92cf32ce564a1827eedb5ee19a01
Signed-off-by: Jose
input: rk8xx pwrkey: add some optimization
1. add key name and type;
2. clear both fall and rise interrupt when detect rise.
Change-Id: I0698f3decc4b92cf32ce564a1827eedb5ee19a01
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
show more ...
|
| e5f330c4 | 12-Nov-2015 |
Bin Meng <bmeng.cn@gmail.com> |
input: Ban digit numbers if 'Num Lock' is not on
When 'Num Lock' is not on, we should not send these digit numbers
(0-9 and dot) to the output buffer.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
A
input: Ban digit numbers if 'Num Lock' is not on
When 'Num Lock' is not on, we should not send these digit numbers
(0-9 and dot) to the output buffer.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 377a0696 | 12-Nov-2015 |
Bin Meng <bmeng.cn@gmail.com> |
input: Change LED state bits to conform i8042 compatible keyboard
When sending LED update command to an i8042 compatible keyboard,
bit1 is 'Num Lock' and bit2 is 'Caps Lock' in the data byte. But
in
input: Change LED state bits to conform i8042 compatible keyboard
When sending LED update command to an i8042 compatible keyboard,
bit1 is 'Num Lock' and bit2 is 'Caps Lock' in the data byte. But
input library defines bit1 as 'Caps Lock' and bit2 as 'Num Lock'.
This causes a wrong LED to be set on an i8042 compatible keyboard.
Change the LED state bits to be i8042 compatible, and change the
keyboard flags as well.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|