linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Stefan Brüns" <stefan.bruens@rwth-aachen.de>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: atkbd - correct MSC_SCAN events for force_release keys
Date: Thu, 23 Oct 2014 16:44:59 -0700	[thread overview]
Message-ID: <20141023234459.GB9463@dtor-ws> (raw)
In-Reply-To: <2149226.863NAkGi8a@pebbles.site>

On Sat, Oct 18, 2014 at 12:48:59AM +0200, Stefan Brüns wrote:
> On Sunday, September 28, 2014 11:13:24 PM you wrote:
> > Without the change either no scancode would be reported on release
> > of force_release keys, or - if the key is marked as force_release
> > erroneously - the release event and the scancode would be reported
> > in separate reports to the input layer.
> > 
> > Signed-off-by: Stefan Brüns <stefan.bruens@rwth-aachen.de>
> > ---
> >  drivers/input/keyboard/atkbd.c | 6 ++++--
> >  1 file changed, 4 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
> > index 2dd1d0d..6375ae6 100644
> > --- a/drivers/input/keyboard/atkbd.c
> > +++ b/drivers/input/keyboard/atkbd.c
> > @@ -456,8 +456,9 @@ static irqreturn_t atkbd_interrupt(struct serio *serio, unsigned char data,
> >  
> >  	keycode = atkbd->keycode[code];
> >  
> > -	if (keycode != ATKBD_KEY_NULL)
> > -		input_event(dev, EV_MSC, MSC_SCAN, code);
> > +	if (!(atkbd->release && test_bit(code, atkbd->force_release_mask)))
> > +		if (keycode != ATKBD_KEY_NULL)
> > +			input_event(dev, EV_MSC, MSC_SCAN, code);
> >  
> >  	switch (keycode) {
> >  	case ATKBD_KEY_NULL:
> > @@ -511,6 +512,7 @@ static irqreturn_t atkbd_interrupt(struct serio *serio, unsigned char data,
> >  		input_sync(dev);
> >  
> >  		if (value && test_bit(code, atkbd->force_release_mask)) {
> > +			input_event(dev, EV_MSC, MSC_SCAN, code);
> >  			input_report_key(dev, keycode, 0);
> >  			input_sync(dev);
> >  		}
> > 
> 
> Ping!
> 
> Kind regards,

I do not see the original patch mail, could you please resend (and CC
me)?

Thanks.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-10-23 23:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28 21:13 [PATCH] Input: atkbd - correct MSC_SCAN events for force_release keys Stefan Brüns
2014-10-17 22:48 ` Stefan Brüns
2014-10-23 23:44   ` Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-16 22:18 Stefan Brüns
2014-11-17  2:25 ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141023234459.GB9463@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=stefan.bruens@rwth-aachen.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).