linux-kernel - Re: [PATCHv2 4/3] Input: omap4-keypad - scan the keys in two phases to detect lost key-up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 6 Mar 2020 11:09:52 -0800
From:   Tony Lindgren <tony@...mide.com>
To:     Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:     linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-omap@...r.kernel.org,
        Arthur Demchenkov <spinal.by@...il.com>,
        Merlijn Wajer <merlijn@...zup.org>,
        Pavel Machek <pavel@....cz>,
        Sebastian Reichel <sre@...nel.org>, ruleh <ruleh@....de>
Subject: Re: [PATCHv2 4/3] Input: omap4-keypad - scan the keys in two phases
 to detect lost key-up

* Dmitry Torokhov <dmitry.torokhov@...il.com> [200306 19:05]:
> On Fri, Feb 28, 2020 at 10:02:43AM -0800, Tony Lindgren wrote:
> > In addition to handling errata i689 for idle with state, we must also
> > check for lost key up interrupts on fast key presses.
> > 
> > For example rapidly pressing shift-shift-j can sometimes produce a J
> > instead of j. Let's fix the issue by scanning the keyboard in two
> > phases. First we scan for any key up events that we may have missed,
> > and then we scan for key down events.
> > 
> > Cc: Arthur Demchenkov <spinal.by@...il.com>
> > Cc: Merlijn Wajer <merlijn@...zup.org>
> > Cc: Pavel Machek <pavel@....cz>
> > Cc: Sebastian Reichel <sre@...nel.org>
> > Signed-off-by: Tony Lindgren <tony@...mide.com>
> > ---
> >  drivers/input/keyboard/omap4-keypad.c | 48 ++++++++++++++++++---------
> >  1 file changed, 32 insertions(+), 16 deletions(-)
> > 
> > diff --git a/drivers/input/keyboard/omap4-keypad.c b/drivers/input/keyboard/omap4-keypad.c
> > --- a/drivers/input/keyboard/omap4-keypad.c
> > +++ b/drivers/input/keyboard/omap4-keypad.c
> > @@ -109,6 +109,34 @@ static void kbd_write_irqreg(struct omap4_keypad *keypad_data,
> >  		     keypad_data->base + keypad_data->irqreg_offset + offset);
> >  }
> >  
> > +static void omap4_keypad_scan_state(struct omap4_keypad *keypad_data,
> > +				    unsigned char *key_state,
> > +				    bool down)
> > +{
> > +	struct input_dev *input_dev = keypad_data->input;
> > +	unsigned int col, row, code, changed;
> > +	bool key_down;
> > +
> > +	for (row = 0; row < keypad_data->rows; row++) {
> > +		changed = key_state[row] ^ keypad_data->key_state[row];
> > +		if (!changed)
> > +			continue;
> > +
> > +		for (col = 0; col < keypad_data->cols; col++) {
> > +			if (changed & (1 << col)) {
> 
> 
> Looking at all too this, key state is 64 bit value, so if we make it a
> bitmap and use "for_each_set_bit()" we can simplify this scanning code.

OK good idea, I'll take a look.

Regards,

Tony