From: Rob Herring <robh@kernel.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-kernel@vger.kernel.org, linux-amarula@amarulasolutions.com,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Haibo Chen <haibo.chen@nxp.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: input: touchscreen: fsl,imx6ul-tsc: add fsl,glitch-threshold
Date: Wed, 23 Jul 2025 00:03:19 -0500 [thread overview]
Message-ID: <20250723050319.GA1239529-robh@kernel.org> (raw)
In-Reply-To: <20250722103706.3440777-3-dario.binacchi@amarulasolutions.com>
On Tue, Jul 22, 2025 at 12:36:16PM +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>
> ---
>
> .../input/touchscreen/fsl,imx6ul-tsc.yaml | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/fsl,imx6ul-tsc.yaml b/Documentation/devicetree/bindings/input/touchscreen/fsl,imx6ul-tsc.yaml
> index 678756ad0f92..2fee2940213f 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/fsl,imx6ul-tsc.yaml
> +++ b/Documentation/devicetree/bindings/input/touchscreen/fsl,imx6ul-tsc.yaml
> @@ -62,6 +62,23 @@ properties:
> description: Number of data samples which are averaged for each read.
> enum: [ 1, 4, 8, 16, 32 ]
>
> + fsl,glitch-threshold:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + default: 0
> + enum: [ 0, 1, 2, 3 ]
> + description: |
> + Indicates the glitch threshold. The threshold is defined by number
> + of clock cycles. A detect signal is only valid if it is exist longer
> + than threshold; otherwise, it is regarded as a glitch.
> + 0: Normal function: 8191 clock cycles
> + Low power mode: 9 clock cycles
> + 1: Normal function: 4095 clock cycles
> + Low power mode: 7 clock cycles
> + 2: Normal function: 2047 clock cycles
> + Low power mode: 5 clock cycles
> + 3: Normal function: 1023 clock cycles
> + Low power mode: 3 clock cycles
Don't we have common properties for this expressed in time? Debounce
time IIRC.
> +
> required:
> - compatible
> - reg
> @@ -94,4 +111,5 @@ examples:
> measure-delay-time = <0xfff>;
> pre-charge-time = <0xffff>;
> touchscreen-average-samples = <32>;
> + fsl,glitch-threshold = <2>;
> };
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-07-23 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 10:36 [PATCH 0/4] Input: imx6ul_tsc - set glitch threshold by dts property Dario Binacchi
2025-07-22 10:36 ` [PATCH 2/4] dt-bindings: input: touchscreen: fsl,imx6ul-tsc: add fsl,glitch-threshold Dario Binacchi
2025-07-23 2:45 ` Bough Chen
2025-07-23 6:14 ` Dario Binacchi
2025-07-23 5:03 ` Rob Herring [this message]
2025-07-23 6:25 ` Dario Binacchi
2025-09-02 6:24 ` 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=20250723050319.GA1239529-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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