From: paul <paul@crapouillou.net>
To: Bastien Nocera <hadess@hadess.net>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: goodix: Check the 'data ready' bit before reading data
Date: Mon, 27 Apr 2015 11:00:26 +0200 [thread overview]
Message-ID: <df24297181d7b061f4c31f7fe118bdf6@mail.crapouillou.net> (raw)
In-Reply-To: <1429966457.2525.54.camel@hadess.net>
Hi Bastien,
Ok, I will send a V2 with a better commit message then.
-Paul
Le 2015-04-25 14:54, Bastien Nocera a écrit :
> On Sat, 2015-04-25 at 12:48 +0200, Paul Cercueil wrote:
>> The MSB of the first byte read via I2C seems to indicate whether the
>> data is valid (or ready) when an interrupt is raised. Previously,
>> this
>> bit was ignored, which resulted in a lot of incorrect detections of
>> "finger removed" events.
>
> This seems correct, but the wording doesn't match the language used in
> the Goodix docs that were posted here some time ago[1].
>
> I would have written:
> The MSB of the first byte read via I2C at the coordinates address
> indicate 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.
>
> And for the commit subject:
> input: goodix: Check the 'buffer status' bit before reading data
>
> This seems correct otherwise.
>
> Signed-off-by: Bastien Nocera <hadess@hadess.net>
>
> with the fixed commit message/subject
>
> [1]: Linked from the device tree support patch:
> https://patchwork.ozlabs.org/patch/446838/
> Page 16, table c, 0x814E is what we read for coordinates
>
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> ---
>> drivers/input/touchscreen/goodix.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/input/touchscreen/goodix.c
>> b/drivers/input/touchscreen/goodix.c
>> index ca19668..9fa6c5f 100644
>> --- a/drivers/input/touchscreen/goodix.c
>> +++ b/drivers/input/touchscreen/goodix.c
>> @@ -98,6 +98,9 @@ static int goodix_ts_read_input_report(struct
>> goodix_ts_data *ts, u8 *data)
>> return error;
>> }
>>
>> + if (!(data[0] & 0x80))
>> + return -EAGAIN;
>> +
>> touch_num = data[0] & 0x0f;
>> if (touch_num > GOODIX_MAX_CONTACTS)
>> return -EPROTO;
prev parent reply other threads:[~2015-04-27 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 10:48 Paul Cercueil
2015-04-25 12:54 ` Bastien Nocera
2015-04-27 9:00 ` paul [this message]
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=df24297181d7b061f4c31f7fe118bdf6@mail.crapouillou.net \
--to=paul@crapouillou.net \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®