From: Bastien Nocera <hadess@hadess.net>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] input: goodix: Check the 'buffer status' bit before reading data
Date: Fri, 01 May 2015 16:13:55 +0200 [thread overview]
Message-ID: <1430489635.3945.3.camel@hadess.net> (raw)
In-Reply-To: <1430484036-17541-1-git-send-email-paul@crapouillou.net>
On Fri, 2015-05-01 at 14:40 +0200, Paul Cercueil wrote:
> The MSB of the first byte read via I2C at the coordinates address
> indicates whether the data is valid or ready (called "buffer status"
> in
> the datasheets) when an interrupt is raised. Previously, this bit was
> ignored, which resulted in a lot of incorrect detections of "finger
> removed" events.
>
> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
Signed-off-by: Bastien Nocera <hadess@hadess.net>
next prev parent reply other threads:[~2015-05-01 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 12:40 [PATCH v2] input: goodix: Check the 'buffer status' bit before reading data Paul Cercueil
2015-05-01 14:13 ` Bastien Nocera [this message]
2015-05-06 23:54 ` 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=1430489635.3945.3.camel@hadess.net \
--to=hadess@hadess.net \
--cc=dmitry.torokhov@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).