From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: David Heidelberg <david@ixit.cz>
Cc: linux-input@vger.kernel.org
Subject: Re: Double tap to wake optionality
Date: Sun, 13 Sep 2026 16:33:23 -0700 [thread overview]
Message-ID: <aqcxlFLHh3V5vQvt@google.com> (raw)
In-Reply-To: <4f9e942c-823e-4ab1-81ed-184b5f8388d6@ixit.cz>
Hi David,
On Mon, Sep 07, 2026 at 12:02:12AM +0200, David Heidelberg wrote:
> Hello!
>
> Most of touchscreens has ability to jump into low power mode and get woken
> up by gesture (such as double tap).
>
> I wonder about suggestion what property should drivers use to implement this
> policy where driver doesn't have to jump into low-power mode but completely
> power-off (and save battery). My thinking was something such as
>
> /sys/class/input/inputX/gesture_to_wake
> (while gesture sounds a bit weird, it seems that TS are capable to recognize
> different patterns, not only double-tap).
>
>
> userspace
> │
> │ gesture_to_wake = 1
> ▼
> touchscreen driver
> │
> ┌────────────┴────────────┐
> │ │
> gesture ON gesture OFF
> │ │
> ▼ ▼
> low-power TS mode complete power-off
> │
> ▼
> IRQ configured
> as wake source
How is it different from the power/wakeup device attribute? Device's
suspend routines check device_may_wakeup() and then either completely
power off controllers or configure them for wake up.
How exactly wakeup is handled - any touch, or double-tap, or something
else - is up to the controller and its firmware.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-09-13 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 22:02 Double tap to wake optionality David Heidelberg
2026-09-13 23:33 ` Dmitry Torokhov [this message]
2026-09-21 11:19 ` David Heidelberg
2026-09-21 16:20 ` Dmitry Torokhov
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=aqcxlFLHh3V5vQvt@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=david@ixit.cz \
--cc=linux-input@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox