From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Aniroop Mathur <a.mathur@samsung.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
aniroop.mathur@gmail.com
Subject: Re: [PATCH] Input: evdev - Avoid duplicate checking of empty SYN_REPORT
Date: Sat, 2 Jan 2016 20:31:06 -0800 [thread overview]
Message-ID: <20160103043106.GA23680@dtor-ws> (raw)
In-Reply-To: <1451517958-2173-1-git-send-email-a.mathur@samsung.com>
Hi Aniroop,
On Thu, Dec 31, 2015 at 04:55:58AM +0530, Aniroop Mathur wrote:
> Input core already drops empty syn_report event so there is no need
> to check again for dropping empty syn_report event in evdev handler
> for all clients on every new event.
This reasoning is flawed: if all events from the packet are filtered out
for the given client we should be suppressing EV_SYN/SYN_REPORT pair as
well.
Thanks.
>
> Signed-off-by: Aniroop Mathur <a.mathur@samsung.com>
> ---
> drivers/input/evdev.c | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/drivers/input/evdev.c b/drivers/input/evdev.c
> index e9ae3d5..6e242b7 100644
> --- a/drivers/input/evdev.c
> +++ b/drivers/input/evdev.c
> @@ -276,13 +276,8 @@ static void evdev_pass_values(struct evdev_client *client,
> if (__evdev_is_filtered(client, v->type, v->code))
> continue;
>
> - if (v->type == EV_SYN && v->code == SYN_REPORT) {
> - /* drop empty SYN_REPORT */
> - if (client->packet_head == client->head)
> - continue;
> -
> + if (v->type == EV_SYN && v->code == SYN_REPORT)
> wakeup = true;
> - }
>
> event.type = v->type;
> event.code = v->code;
> --
> 2.6.2
>
--
Dmitry
prev parent reply other threads:[~2016-01-03 4:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 23:25 [PATCH] Input: evdev - Avoid duplicate checking of empty SYN_REPORT Aniroop Mathur
2016-01-03 4:31 ` Dmitry Torokhov [this message]
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=20160103043106.GA23680@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=a.mathur@samsung.com \
--cc=aniroop.mathur@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).