HW: i.MX7 SabreSD
SW: Android N7.1.1_1.0.0
There is KPP module on i.MX7, but NXP reference board didn't have it. We reworked a "keypad" and has the demo.
For testing, launch an app in Android that can accept text input. KPP also supports multiple input, the "A" is showed by pressing "shift" + "a".
As a side note,
1. The input device driver is drivers/input/keyboard/imx_keypad.c
2. The input event driver is drivers/tty/vt/keyboard.c
Original Attachment has been moved to: 0001-Enable-KPP-on-i.MX7.patch.zip
Did you test the pressing "shift" + " f " and "shift" + " g " ?
If yes, could you show me it in image like above ?
Let me find some time to check it again next week. Multiple key is having issues on your board?
Sorry for late reply.
Did you have time to check it ?
Not on our board, it's on my customer board.
The test result is shown as below, multiple key can be detected if it's not on the same row.
Thank you for testing.
Unfortunately, my customer need multiple key detect on the same row.
The conclusion is i.MX7 can't detect multiple key on the same row.
Am I correct ?
I think it is a bug but not limitation. You can submit another ticket for it.
By any chance, have you submitted a new ticket about this issue?
Thanks and regards!
Hi Paulo Knirsch
I posted Case:00139023.
Could you follow it ?
What I want to know is whether the workaround need additional hardware or not.
Attach the patch for fixing multiple key detection on the same row, 0001-Keypad-support-key-detection-at-the-same-row-on-i.MX.patch
Thank you for providing the patch.
I want to test the patch but unfortunately, I don't have any environment for test.
So could you test the pressing "shift" + " f " and "shift" + " g " again ?
I've tested all the keys, it works correctly.
Thank you for quick response.
Could you show me the image like above ?
Also I have additional question.
The workaround in the thread is without any additional hardware.
I need info that whether user need an additional hardware for detecting multiple keys in the same row or not.
Is it still discussing ?
There's no need for additional HW rework.
I can't test in my environment so I need proof.
Could you follow this thread again ?