From: Rob Herring <robh@kernel.org>
To: Leif Middelschulte <leif.middelschulte@klsmartin.com>
Cc: dmitry.torokhov@gmail.com, devicetree@vger.kernel.org,
linux-input@vger.kernel.org, mark.rutland@arm.com
Subject: Re: [PATCH 09/10] dt-bindings: input: touchscreen: stmpe: add tracking index
Date: Fri, 14 Jun 2019 13:58:59 -0600 [thread overview]
Message-ID: <20190614195859.GA6351@bogus> (raw)
In-Reply-To: <20190527161938.31871-5-leif.middelschulte@klsmartin.com>
On Mon, May 27, 2019 at 06:19:37PM +0200, Leif Middelschulte wrote:
> The tracking index is a "minimum" distance two touch
> points need to have in order for the second to be valid.
> This adds the corresponding binding property documentation.
>
> Signed-off-by: Leif Middelschulte <leif.middelschulte@klsmartin.com>
> ---
> .../bindings/input/touchscreen/stmpe.txt | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/stmpe.txt b/Documentation/devicetree/bindings/input/touchscreen/stmpe.txt
> index 09d2d4f288cc..8696af35a7b8 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/stmpe.txt
> +++ b/Documentation/devicetree/bindings/input/touchscreen/stmpe.txt
> @@ -42,6 +42,21 @@ Optional properties:
> The given window also affects the value range (limits) set
> within the input subsystem which, in turn, affects
> the input resolution calculation on both axes.
> +- st,tracking-index : Minimal distance between the current touch position and the previous
> + touch position. If the distance is shorter than the tracking
> + index, it is discarded. The tracking is calculated by summation
> + of the horizontal and vertical movement.
> + If pressure reporting is enabled (X/Y/Z), an increase in pressure
> + override the movement tracking and report the new data set, even
> + if X/Y is within the previous tracking index.
> + 0 -> disabled
> + 1 -> 4
> + 4 -> 8
> + 3 -> 16
> + 4 -> 32
> + 5 -> 64
> + 6 -> 92
> + 7 -> 127
This is what touchscreen-fuzz-x/y is for.
> - touchscreen-inverted-x: X axis is inverted (boolean)
> - touchscreen-inverted-y: Y axis is inverted (boolean)
> - touchscreen-swapped-x-y: X and Y axis are swapped (boolean)
> --
> 2.21.0
>
next prev parent reply other threads:[~2019-06-14 19:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 16:07 [PATCH 00/10] input: touchscreen: stmpe: ext. features Leif Middelschulte
2019-05-27 16:07 ` [PATCH 01/10] dt-bindings: input: touchscreen: stmpe: add touch window configuration Leif Middelschulte
2019-06-14 19:48 ` Rob Herring
2019-06-19 11:55 ` Middelschulte, Leif
2019-06-19 13:51 ` Rob Herring
2019-06-24 10:33 ` Middelschulte, Leif
2019-05-27 16:07 ` [PATCH 02/10] Input: stmpe-ts - implement touch window configuration support Leif Middelschulte
2019-05-27 16:07 ` [PATCH 03/10] dt-bindings: input: touchscreen: stmpe: add resolution support Leif Middelschulte
2019-06-14 19:55 ` Rob Herring
2019-06-19 12:33 ` Middelschulte, Leif
2019-05-27 16:07 ` [PATCH 04/10] Input: stmpe-ts - implement " Leif Middelschulte
2019-05-27 16:19 ` [PATCH 05/10] dt-bindings: input: touchscreen: stmpe: add XY mode Leif Middelschulte
2019-05-27 16:19 ` [PATCH 06/10] Input: stmpe-ts - implement XY acquisition mode Leif Middelschulte
2019-05-27 16:19 ` [PATCH 07/10] dt-bindings: input: touchscreen: stmpe: add axes inversion and swap Leif Middelschulte
2019-06-14 19:56 ` Rob Herring
2019-05-27 16:19 ` [PATCH 08/10] Input: stmpe-ts - axes inversion and swapping Leif Middelschulte
2019-05-27 16:19 ` [PATCH 09/10] dt-bindings: input: touchscreen: stmpe: add tracking index Leif Middelschulte
2019-06-14 19:58 ` Rob Herring [this message]
2019-06-19 12:47 ` Middelschulte, Leif
2019-06-19 13:46 ` Rob Herring
2019-06-24 11:44 ` Middelschulte, Leif
2019-06-14 19:55 ` [PATCH 05/10] dt-bindings: input: touchscreen: stmpe: add XY mode Rob Herring
2019-05-27 16:22 ` [PATCH 10/10] Input: stmpe-ts - implement tracking index Leif Middelschulte
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=20190614195859.GA6351@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=leif.middelschulte@klsmartin.com \
--cc=linux-input@vger.kernel.org \
--cc=mark.rutland@arm.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).