From: Rob Herring <robh@kernel.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-kernel@vger.kernel.org, Frank Li <Frank.Li@nxp.com>,
linux-amarula@amarulasolutions.com,
Conor Dooley <conor.dooley@microchip.com>,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Javier Carrasco <javier.carrasco@wolfvision.net>,
Jeff LaBundy <jeff@labundy.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v5 3/6] dt-bindings: touchscreen: add touchscreen-glitch-threshold-ns property
Date: Thu, 18 Sep 2025 15:04:45 -0500 [thread overview]
Message-ID: <20250918200445.GA2529753-robh@kernel.org> (raw)
In-Reply-To: <20250918155240.2536852-4-dario.binacchi@amarulasolutions.com>
On Thu, Sep 18, 2025 at 05:52:31PM +0200, Dario Binacchi wrote:
> Add support for glitch threshold configuration. A detected signal is valid
> only if it lasts longer than the set threshold; otherwise, it is regarded
> as a glitch.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> ---
>
> Changes in v5:
> - Add Acked-by tag of Conor Dooley
>
> Changes in v2:
> - Added in v2.
>
> .../devicetree/bindings/input/touchscreen/touchscreen.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/touchscreen.yaml b/Documentation/devicetree/bindings/input/touchscreen/touchscreen.yaml
> index 3e3572aa483a..a60b4d08620d 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/touchscreen.yaml
> +++ b/Documentation/devicetree/bindings/input/touchscreen/touchscreen.yaml
> @@ -206,6 +206,10 @@ properties:
>
> unevaluatedProperties: false
>
> + touchscreen-glitch-threshold-ns:
> + description: Minimum duration in nanoseconds a signal must remain stable
> + to be considered valid.
What's wrong with debounce-delay-ms?
next prev parent reply other threads:[~2025-09-18 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 15:52 [PATCH v5 0/6] Input: imx6ul_tsc - set glitch threshold by dts property Dario Binacchi
2025-09-18 15:52 ` [PATCH v5 1/6] Input: imx6ul_tsc - fix typo in register name Dario Binacchi
2025-09-18 15:52 ` [PATCH v5 2/6] Input: imx6ul_tsc - use BIT, FIELD_{GET,PREP} and GENMASK macros Dario Binacchi
2025-09-18 15:52 ` [PATCH v5 3/6] dt-bindings: touchscreen: add touchscreen-glitch-threshold-ns property Dario Binacchi
2025-09-18 20:04 ` Rob Herring [this message]
2025-09-18 20:37 ` Dario Binacchi
2025-09-19 14:38 ` Rob Herring
2025-09-19 15:12 ` Dario Binacchi
2025-09-19 20:44 ` Rob Herring
2025-09-20 9:39 ` Dario Binacchi
2025-09-22 15:07 ` Rob Herring
2025-09-18 15:52 ` [PATCH v5 4/6] dt-bindings: touchscreen: fsl,imx6ul-tsc: support glitch thresold Dario Binacchi
2025-09-18 15:52 ` [PATCH v5 5/6] ARM: dts: imx6ull-engicam-microgea-bmm: set touchscreen glitch threshold Dario Binacchi
2025-09-18 15:52 ` [PATCH v5 6/6] Input: imx6ul_tsc - set glitch threshold by DTS property Dario Binacchi
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=20250918200445.GA2529753-robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=javier.carrasco@wolfvision.net \
--cc=jeff@labundy.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amarula@amarulasolutions.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.