linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "DISTEC Inan, Ahmet" <Inan@distec.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, Ahmet Inan <xdsopl@gmail.com>
Subject: Re: [PATCH] Input: Add I2C attached EETI EXC3000 multi touch driver
Date: Fri, 22 Sep 2017 14:48:53 +0200	[thread overview]
Message-ID: <20170922124852.2bsx45jeqye6qcss@dev-ai1.datadisplay.de> (raw)
In-Reply-To: <20170921211551.GB15858@dtor-ws>

Dear Dmitry,

> > It is important not to rely on the i2c_master_recv return value:
> > Ignoring failed transfers sometimes causes hanging touch events, as the
> > controller thinks that the transfer succeeded and won't resend the event.
> 
> This statement worries me, because you are basically end up reporting
> garbage. Does the controller sends all active contacts in each frame, or
> only changed ones? You can use INPUT_MT_DROP_UNUSED to let input core
> automatically drop contacts that were not reported within the last
> frame. And fire up a timer to release everything if last transfer errors
> out.
Thank you for the suggestions. I indeed felt uncomfortable about
ignoring the return value of i2c_master_recv() but INPUT_MT_DROP_UNUSED
helped and now it works awesome!

> > +	input_set_abs_params(input, ABS_X, 0, 4096, 0, 0);
> > +	input_set_abs_params(input, ABS_Y, 0, 4096, 0, 0);
> > +	input_set_abs_params(input, ABS_MT_POSITION_X, 0, 4096, 0, 0);
> > +	input_set_abs_params(input, ABS_MT_POSITION_Y, 0, 4096, 0, 0);
> 
> 	touchscreen_parse_properties() ?

Need do wrap my head around this. I've send you a new patch with all
(but this one) suggested improvements. I will send send you a follow-up
patch with touchscreen_parse_properties() if you're OK with the current
patch and want to merge it.

Best Regards,

Ahmet


  reply	other threads:[~2017-09-22 12:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 13:51 [PATCH] Input: Add I2C attached EETI EXC3000 multi touch driver Ahmet Inan
2017-09-21 21:15 ` Dmitry Torokhov
2017-09-22 12:48   ` DISTEC Inan, Ahmet [this message]
2017-09-22 14:18     ` DISTEC Inan, Ahmet
2017-09-22 14:52       ` DISTEC Inan, Ahmet
2017-09-25 14:59     ` DISTEC Inan, Ahmet
2017-09-28 13:42     ` DISTEC Inan, Ahmet
  -- strict thread matches above, loose matches on Subject: below --
2017-09-22 12:30 Ahmet Inan
2017-09-22 14:46 Ahmet Inan
2017-09-25 14:39 Ahmet Inan
2017-09-27  6:08 ` Dmitry Torokhov
2017-09-27 12:58   ` DISTEC Inan, Ahmet
2017-09-27 12:36 Ahmet Inan
2017-09-28 15:23 Ahmet Inan
2017-10-05 23:22 ` Rob Herring
2017-10-06  7:43   ` DISTEC Inan, Ahmet

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=20170922124852.2bsx45jeqye6qcss@dev-ai1.datadisplay.de \
    --to=inan@distec.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=xdsopl@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).