From: Javier Carrasco <javier.carrasco@wolfvision.net>
To: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Linus Walleij <linus.walleij@linaro.org>,
Uwe Kleine-g <u.kleine-koenig@pengutronix.de>,
Michael Riesch <michael.riesch@wolfvision.net>,
Javier Carrasco <javier.carrasco@wolfvision.net>
Subject: [PATCH 0/2] Input: st1232: wakeup in Suspend to idle
Date: Mon, 3 Apr 2023 14:47:05 +0200 [thread overview]
Message-ID: <20230403124707.102986-1-javier.carrasco@wolfvision.net> (raw)
The st1232 touchscreen provides an interrupt line that can be configured
as a wakeup source, and currently it is possible to use this mechanism in
"Suspend to RAM" and "Hibernate" power states.
Unfortunately, that does not work in "Suspend to idle" (freeze) because
the device driver disables the interrupts in its suspend callback.
Given that the interrupt handling prior to entering the mentioned power
state modes is managed by the power subsystem, the irq enabling/disabling
can be removed from the touchscreen driver, allowing the device to work
as a wakeup source in "Suspend to idle".
Given that the st1232 device driver does not reflect its wakeup events
in sysfs, this series also adds pm_wakeup_event to the interrupt
handler.
These changes have been successfully tested with an ST1624-N32C and a
Rockchip-based platform.
Javier Carrasco (2):
Input: st1232 - remove enable/disable irq in resume/suspend callbacks
Input: st1232 - add wake up event counting
drivers/input/touchscreen/st1232.c | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
--
2.37.2
next reply other threads:[~2023-04-03 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 12:47 Javier Carrasco [this message]
2023-04-03 12:47 ` [PATCH 1/2] Input: st1232 - remove enable/disable irq in resume/suspend callbacks Javier Carrasco
2023-04-03 12:47 ` [PATCH 2/2] Input: st1232 - add wake up event counting Javier Carrasco
2023-04-18 4:12 ` [PATCH 0/2] Input: st1232: wakeup in Suspend to idle Javier Carrasco Cruz
2023-05-10 8:42 ` Javier Carrasco
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=20230403124707.102986-1-javier.carrasco@wolfvision.net \
--to=javier.carrasco@wolfvision.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.riesch@wolfvision.net \
--cc=u.kleine-koenig@pengutronix.de \
/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