vasilito
f31522130f
Build system (5 gaps hardened): - COOKBOOK_OFFLINE defaults to true (fork-mode) - normalize_patch handles diff -ruN format - New 'repo validate-patches' command (25/25 relibc patches) - 14 patched Qt/Wayland/display recipes added to protected list - relibc archive regenerated with current patch chain Boot fixes (fixable): - Full ISO EFI partition: 16 MiB → 1 MiB (matches mini, BIOS hardcoded 2 MiB offset) - D-Bus system bus: absolute /usr/bin/dbus-daemon path (was skipped) - redbear-sessiond: absolute /usr/bin/redbear-sessiond path (was skipped) - daemon framework: silenced spurious INIT_NOTIFY warnings for oneshot_async services (P0-daemon-silence-init-notify.patch) - udev-shim: demoted INIT_NOTIFY warning to INFO (expected for oneshot_async) - relibc: comprehensive named semaphores (sem_open/close/unlink) replacing upstream todo!() stubs - greeterd: Wayland socket timeout 15s → 30s (compositor DRM wait) - greeter-ui: built and linked (header guard unification, sem_compat stubs removed) - mc: un-ignored in both configs, fixed glib/libiconv/pcre2 transitive deps - greeter config: removed stale keymapd dependency from display/greeter services - prefix toolchain: relibc headers synced, _RELIBC_STDLIB_H guard unified Unfixable (diagnosed, upstream): - i2c-hidd: abort on no-I2C-hardware (QEMU) — process::exit → relibc abort - kded6/greeter-ui: page fault 0x8 — Qt library null deref - Thread panics fd != -1 — Rust std library on Redox - DHCP timeout / eth0 MAC — QEMU user-mode networking - hwrngd/thermald — no hardware RNG/thermal in VM - live preload allocation — BIOS memory fragmentation, continues on demand
57 lines
2.8 KiB
ReStructuredText
57 lines
2.8 KiB
ReStructuredText
|
|
.. _button_debouncing:
|
|
|
|
==============================================================================
|
|
Button debouncing
|
|
==============================================================================
|
|
|
|
Physical buttons experience wear-and-tear with usage. On some devices this
|
|
can result in an effect called "contact bouncing" or "chatter". This effect
|
|
can cause the button to send multiple events within a short time frame, even
|
|
though the user only pressed or clicked the button once. This effect can be
|
|
counteracted by "debouncing" the buttons, usually by ignoring erroneous
|
|
events.
|
|
|
|
libinput provides two methods of debouncing buttons, referred to as the
|
|
"bounce" and "spurious" methods:
|
|
|
|
- In the "bounce" method, libinput monitors hardware bouncing on button
|
|
state changes, i.e. when a user clicks or releases a button. For example,
|
|
if a user presses a button but the hardware generates a
|
|
press-release-press sequence in quick succession, libinput ignores the
|
|
release and second press event. This method is always enabled.
|
|
- in the "spurious" method, libinput detects spurious releases of a button
|
|
while the button is physically held down by the user. These releases are
|
|
immediately followed by a press event. libinput monitors for these events
|
|
and ignores the release and press event. This method is disabled by
|
|
default and enables once libinput detects the first faulty event sequence.
|
|
|
|
The "bounce" method guarantees that all press events are delivered
|
|
immediately and most release events are delivered immediately. The
|
|
"spurious" method requires that release events are delayed, libinput thus
|
|
does not enable this method unless a faulty event sequence is detected. A
|
|
message is printed to the log when spurious deboucing was detected.
|
|
|
|
libinput's debouncing is supposed to correct hardware damage or
|
|
substandard hardware. Debouncing also exists as an accessibility feature
|
|
but the requirements are different. In the accessibility feature, multiple
|
|
physical key presses, usually caused by involuntary muscle movement, must be
|
|
filtered to only one key press. This feature must be implemented higher in
|
|
the stack, libinput is limited to hardware debouncing.
|
|
|
|
Below is an illustration of the button debouncing modes to show the relation
|
|
of the physical button state and the application state. Where applicable, an
|
|
extra line is added to show the timeouts used by libinput that
|
|
affect the button state handling. The waveform's high and low states
|
|
correspond to the buttons 'pressed' and 'released' states, respectively.
|
|
|
|
.. figure:: button-debouncing-wave-diagram.svg
|
|
:align: center
|
|
|
|
Diagram illustrating button debouncing
|
|
|
|
|
|
Some devices send events in bursts, erroneously triggering the button
|
|
debouncing detection. Please :ref:`file a bug <reporting_bugs>` if that
|
|
occurs for your device.
|