From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Bastien Nocera <hadess@hadess.net>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: goodix: Poll the 'buffer status' bit before reading data
Date: Thu, 30 Mar 2017 15:48:00 -0700 [thread overview]
Message-ID: <20170330224800.GA15258@dtor-ws> (raw)
In-Reply-To: <20170330133349.19931-1-paul@crapouillou.net>
On Thu, Mar 30, 2017 at 03:33:49PM +0200, Paul Cercueil wrote:
> The Goodix panel triggers an interrupt on touch events. However, its
> registers will contain the valid values a short time after the
> interrupt, and not when it's raised. At that moment, the 'buffer status'
> bit is set.
Yay for awesome hardware.
>
> Previously, if the 'buffer status' bit was not set when the registers
> were read, the data was discarded and no input event was emitted,
> causing "finger down" or "finger up" events to be missed sometimes.
>
> This went unnoticed until v4.9, as the DesignWare I2C driver commonly
> used with this driver had enough latency for that bug to never trigger.
>
> Now, in the IRQ handler we will poll (with a timeout) the 'buffer status'
> bit and process the data of the panel as soon as this bit gets set.
>
> Note that the Goodix panel will send a few spurious interrupts after the
> 'finger up' event, in which the 'buffer status' bit will never be set.
>
> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> ---
> drivers/input/touchscreen/goodix.c | 30 +++++++++++++++++++++++-------
> 1 file changed, 23 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/input/touchscreen/goodix.c b/drivers/input/touchscreen/goodix.c
> index 240b16f3ee97..7a8b89b87c2f 100644
> --- a/drivers/input/touchscreen/goodix.c
> +++ b/drivers/input/touchscreen/goodix.c
> @@ -195,18 +195,34 @@ static int goodix_get_cfg_len(u16 id)
>
> static int goodix_ts_read_input_report(struct goodix_ts_data *ts, u8 *data)
> {
> + unsigned int timeout = 100;
> int touch_num;
> int error;
>
> - error = goodix_i2c_read(ts->client, GOODIX_READ_COOR_ADDR, data,
> + /* The 'buffer status' bit, which indicates that the data is valid, is
> + * not set as soon as the interrupt is raised, but slightly after.
> + */
> + do {
> + error = goodix_i2c_read(ts->client, GOODIX_READ_COOR_ADDR, data,
> GOODIX_CONTACT_SIZE + 1);
> - if (error) {
> - dev_err(&ts->client->dev, "I2C transfer error: %d\n", error);
> - return error;
> - }
> + if (error) {
> + dev_err(&ts->client->dev, "I2C transfer error: %d\n",
> + error);
> + return error;
> + }
>
> - if (!(data[0] & 0x80))
> - return -EAGAIN;
> + if (data[0] & 0x80)
> + break;
> +
> + usleep_range(100, 200);
What is the typical delay between IRQ and data being ready? 100 repeats
suggest that poll interval is too small.
> + } while (--timeout);
> +
> + if (!timeout) {
> + /* The Goodix panel will send spurious interrupts after a
> + * 'finger up' event, which will always cause a timeout.
> + */
> + return 0;
> + }
>
> touch_num = data[0] & 0x0f;
> if (touch_num > ts->max_touch_num)
> --
> 2.11.0
>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2017-03-30 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 13:33 [PATCH] input: goodix: Poll the 'buffer status' bit before reading data Paul Cercueil
2017-03-30 22:48 ` Dmitry Torokhov [this message]
2017-03-31 10:18 ` Paul Cercueil
2017-06-19 22:41 ` Bastien Nocera
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=20170330224800.GA15258@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@crapouillou.net \
/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