linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hutterer <peter.hutterer@who-t.net>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Jiri Kosina <jikos@kernel.org>,
	Andrew Duggan <aduggan@synaptics.com>,
	Oscar Morante <spacepluk@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC
Date: Mon, 28 May 2018 09:12:00 +1000	[thread overview]
Message-ID: <20180527231200.GA13676@jelly> (raw)
In-Reply-To: <20180525125106.18008-1-benjamin.tissoires@redhat.com>

On Fri, May 25, 2018 at 02:51:06PM +0200, Benjamin Tissoires wrote:
> When we receive a RMI4 report, we should not unconditionally send an
> input_sync event. Instead, we should let the rmi4 transport layer do it
> for us.
> 
> This fixes a situation where we might receive X in a report and the rest
> in a subsequent one. And this messes up user space.
> 
> Link: https://bugs.freedesktop.org/show_bug.cgi?id=100436
> 
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> ---

yes please! 

Acked-by: Peter Hutterer <peter.hutterer@who-t.net>

Cheers,
   Peter

> 
> Hi,
> 
> Oscar, do you mind if we add your "Tested-by: Oscar Morante <your@email>"?
> 
> Andrew, can you check for any sides effects please?
> 
> Cheers,
> Benjamin
> 
>  drivers/hid/hid-rmi.c | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/drivers/hid/hid-rmi.c b/drivers/hid/hid-rmi.c
> index 9c9362149641..9e33165250a3 100644
> --- a/drivers/hid/hid-rmi.c
> +++ b/drivers/hid/hid-rmi.c
> @@ -413,6 +413,24 @@ static int rmi_event(struct hid_device *hdev, struct hid_field *field,
>  	return 0;
>  }
>  
> +static void rmi_report(struct hid_device *hid, struct hid_report *report)
> +{
> +	struct hid_field *field = report->field[0];
> +
> +	if (!(hid->claimed & HID_CLAIMED_INPUT))
> +		return;
> +
> +	switch (report->id) {
> +	case RMI_READ_DATA_REPORT_ID:
> +		/* fall-through */
> +	case RMI_ATTN_REPORT_ID:
> +		return;
> +	}
> +
> +	if (field && field->hidinput && field->hidinput->input)
> +		input_sync(field->hidinput->input);
> +}
> +
>  #ifdef CONFIG_PM
>  static int rmi_suspend(struct hid_device *hdev, pm_message_t message)
>  {
> @@ -637,6 +655,7 @@ static int rmi_probe(struct hid_device *hdev, const struct hid_device_id *id)
>  	hid_set_drvdata(hdev, data);
>  
>  	hdev->quirks |= HID_QUIRK_NO_INIT_REPORTS;
> +	hdev->quirks |= HID_QUIRK_NO_INPUT_SYNC;
>  
>  	ret = hid_parse(hdev);
>  	if (ret) {
> @@ -744,6 +763,7 @@ static struct hid_driver rmi_driver = {
>  	.remove			= rmi_remove,
>  	.event			= rmi_event,
>  	.raw_event		= rmi_raw_event,
> +	.report			= rmi_report,
>  	.input_mapping		= rmi_input_mapping,
>  	.input_configured	= rmi_input_configured,
>  #ifdef CONFIG_PM
> -- 
> 2.14.3
> 

  reply	other threads:[~2018-05-27 23:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 12:51 [PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC Benjamin Tissoires
2018-05-27 23:12 ` Peter Hutterer [this message]
2018-05-28 16:38 ` Benjamin Tissoires
2018-05-30  6:56 ` Jiri Kosina

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=20180527231200.GA13676@jelly \
    --to=peter.hutterer@who-t.net \
    --cc=aduggan@synaptics.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spacepluk@gmail.com \
    /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).