On Wed, Sep 10, 2025 at 03:58:36PM +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
> +
does any property in input/touchscreen/touchscreen.yaml use as it?
Suppose all touch screen have similar property to filiter out glitch.
Frank
> 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
>