Message ID | 20250918155240.2536852-4-dario.binacchi@amarulasolutions.com |
---|---|
State | New |
Headers | show |
Series |
|
Related | show |
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? To unsubscribe from this group and stop receiving emails from it, send an email to linux-amarula+unsubscribe@amarulasolutions.com.
On Thu, Sep 18, 2025 at 10:04 PM Rob Herring <robh@kernel.org> wrote: > > 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? Do you mean that I should rename touchscreen-glitch-threshold-ns to debounce-delay-ms? Thanks and regards, Dario
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. + dependencies: touchscreen-size-x: [ touchscreen-size-y ] touchscreen-size-y: [ touchscreen-size-x ]