linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, jinqian@android.com
Subject: Re: [PATCH 3/3] goldfish: multitouch: no extra EV_SYN
Date: Tue, 01 Mar 2016 23:27:13 +0000	[thread overview]
Message-ID: <1456874833.7064.22.camel@linux.intel.com> (raw)
In-Reply-To: <20160226195746.GA3769@dtor-ws>

> >  	input_event(edev->input, type, code, value);
> > -	input_sync(edev->input);
> > +	/*
> > +	 * Send an extra (EV_SYN, SYN_REPORT, 0x0) event
> > +	 * if a key was pressed. Some keyboard device
> > +	 * drivers may only send the EV_KEY event and
> > +	 * not EV_SYN.
> 
> That would be error in that keyboard driver and should be fixed.

Agreed but it's still the case that current and long standing Goldfish
behaviour requires the above.

> > +	 * Note that sending an extra SYN_REPORT is not
> > +	 * necessary nor correct protocol with other
> > +	 * devices such as touchscreens, which will send
> > +	 * their own SYN_REPORT's when sufficient event
> > +	 * information has been collected (e.g., for
> > +	 * touchscreens, when pressure and X/Y coordinates
> > +	 * have been received). Hence, we will only send
> > +	 * this extra SYN_REPORT if type == EV_KEY.
> > +	 */
> > +	if (type == EV_KEY)
> > +		input_sync(edev->input);
> 
> 
> I'd rather we always rely on the host to send the SYN event.

That would certainly make sense for the future.

> > +
> >  	return IRQ_HANDLED;
> >  }
> >  
> > @@ -154,6 +173,15 @@ static int events_probe(struct platform_device
> > *pdev)
> >  
> >  	input_dev->name = edev->name;
> >  	input_dev->id.bustype = BUS_HOST;
> > +	/*
> > +	 * Set the Goldfish Device to be multi-touch.
> > +	 * If we do not issue input_mt_init_slots,
> > +	 * the kernel will filter out needed ABS_MT_SLOT
> > +	 * events when we touch the screen in more than one place,
> > +	 * preventing multi-touch with more than one finger from
> > working.
> > +	 * See drivers/input/input.c:input_handle_abs_event.
> > +	 */
> > +	input_mt_init_slots(input_dev, GOLDFISH_MAX_FINGERS, 0);
> 
> Can we use data retrieved by events_import_abs_params() to set up
> correct number of slots? Also we need error handling. And possibly
> retrieve correct properties to set pass to input_mt_init_slots()...

Again - I agree that makes sense for future versions of Goldfish

Alan


  reply	other threads:[~2016-03-01 23:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 18:49 [PATCH 1/3] input: goldfish_events: add devicetree bindings Alan
2016-02-26 18:49 ` [PATCH 2/3] goldfish: Enable ACPI-based enumeration for goldfish events Alan
2016-02-26 20:06   ` Dmitry Torokhov
2016-02-26 18:50 ` [PATCH 3/3] goldfish: multitouch: no extra EV_SYN Alan
2016-02-26 19:57   ` Dmitry Torokhov
2016-03-01 23:27     ` Alan Cox [this message]
2016-02-26 20:05 ` [PATCH 1/3] input: goldfish_events: add devicetree bindings 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=1456874833.7064.22.camel@linux.intel.com \
    --to=alan@linux.intel.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jinqian@android.com \
    --cc=linux-input@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).