[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <db2456d3-c0bb-7198-7841-056212572682@wolfvision.net>
Date: Wed, 10 May 2023 10:42:14 +0200
From: Javier Carrasco <javier.carrasco@...fvision.net>
To: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Linus Walleij <linus.walleij@...aro.org>,
Uwe Kleine-g <u.kleine-koenig@...gutronix.de>,
Michael Riesch <michael.riesch@...fvision.net>
Subject: Re: [PATCH 0/2] Input: st1232: wakeup in Suspend to idle
Gentle ping.
On 03.04.23 14:47, Javier Carrasco wrote:
> 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(-)
>
Powered by blists - more mailing lists