[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6a7bfad6adee31a10b93f465d35ee8ae@bootlin.com>
Date: Fri, 12 Jul 2024 11:11:44 +0200
From: Kamel BOUHARA <kamel.bouhara@...tlin.com>
To: Jeff LaBundy <jeff@...undy.com>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, Rob Herring
<robh+dt@...nel.org>, Krzysztof Kozlowski
<krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>,
Henrik Rydberg <rydberg@...math.org>, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, Marco Felsch
<m.felsch@...gutronix.de>, catalin.popescu@...ca-geosystems.com,
mark.satterthwaite@...chnetix.com, Thomas Petazzoni
<thomas.petazzoni@...tlin.com>, Gregory Clement
<gregory.clement@...tlin.com>, bsp-development.geo@...ca-geosystems.com
Subject: Re: [PATCH v16 3/3] Input: Add TouchNetix axiom i2c touchscreen
driver
[...]
>>> +/*
>>> + * axiom devices are typically configured to report touches at a
>>> rate
>>> + * of 100Hz (10ms) for systems that require polling for reports.
>>> + * When reports are polled, it will be expected to occasionally
>>> + * observe the overflow bit being set in the reports.
>>> + * This indicates that reports are not being read fast enough.
>>
>> This comment is strange; if reports are not read quickly enough at
>> the default rate, why not set the default rate at the slowest for
>> which the overflow bit is not set?
>>
>
> The rate has been set to the give a good user experience regardless of
> this overflow bit that isn't even processed here.
>
and therefore I might remove the part refering to this overflow bit in
the comment.
Regards,
Kamel
Powered by blists - more mailing lists