From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752310AbeDQIU5 (ORCPT ); Tue, 17 Apr 2018 04:20:57 -0400 Received: from fllnx210.ext.ti.com ([198.47.19.17]:26763 "EHLO fllnx210.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751297AbeDQITM (ORCPT ); Tue, 17 Apr 2018 04:19:12 -0400 Subject: Re: [PATCH v2 3/3] Input: ti_am335x_tsc - Prevent system suspend when TSC is in use To: Dmitry Torokhov CC: "Strashko, Grygorii" , "linux-input@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-omap@vger.kernel.org" , Tony Lindgren References: <20180414095153.32060-1-vigneshr@ti.com> <20180414095153.32060-4-vigneshr@ti.com> <20180416180148.GD77055@dtor-ws> From: Vignesh R Message-ID: <9a306d64-1ffd-d311-5660-aaab3a89e26d@ti.com> Date: Tue, 17 Apr 2018 13:49:55 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180416180148.GD77055@dtor-ws> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 8bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 16 April 2018 11:31 PM, Dmitry Torokhov wrote: > On Sat, Apr 14, 2018 at 03:21:53PM +0530, Vignesh R wrote: >> From: Grygorii Strashko >> >> Prevent system suspend while user has finger on touch screen, >> because TSC is wakeup source and suspending device while in use will >> result in failure to disable the module. >> This patch uses pm_stay_awake() and pm_relax() APIs to prevent and >> resume system suspend as required. > > This looks like common behavior for all touchscreens and many other > input devices, but other systems seem to cope without having to add > pm_stay_awake() and pm_relax(). I wonder why your system requires it and > whether we can generalize this somehow. > Not sure if other touch drivers with IP level wakeup, have been tested in the same way as above scenario. But, if user has finger on touchscreen, its better not to enter suspend until user stops interacting with wakeup source. I see pm_stay_awake()/pm_relax() pair as the only way to stop system suspend when wakeup source is active. Also, one other touchscreen driver(zforce_ts.c) and gpio_keys.c use pm_stay_awake()/pm_relax() pair. Regards Vignesh >> >> Signed-off-by: Grygorii Strashko >> Signed-off-by: Vignesh R >> --- >> >> v2: No changes. >> >>  drivers/input/touchscreen/ti_am335x_tsc.c | 3 +++ >>  1 file changed, 3 insertions(+) >> >> diff --git a/drivers/input/touchscreen/ti_am335x_tsc.c b/drivers/input/touchscreen/ti_am335x_tsc.c >> index dcd9db768169..43b22e071842 100644 >> --- a/drivers/input/touchscreen/ti_am335x_tsc.c >> +++ b/drivers/input/touchscreen/ti_am335x_tsc.c >> @@ -275,6 +275,7 @@ static irqreturn_t titsc_irq(int irq, void *dev) >>        if (status & IRQENB_HW_PEN) { >>                ts_dev->pen_down = true; >>                irqclr |= IRQENB_HW_PEN; >> +             pm_stay_awake(ts_dev->mfd_tscadc->dev); >>        } >>  >>        if (status & IRQENB_PENUP) { >> @@ -284,6 +285,7 @@ static irqreturn_t titsc_irq(int irq, void *dev) >>                        input_report_key(input_dev, BTN_TOUCH, 0); >>                        input_report_abs(input_dev, ABS_PRESSURE, 0); >>                        input_sync(input_dev); >> +                     pm_relax(ts_dev->mfd_tscadc->dev); >>                } else { >>                        ts_dev->pen_down = true; >>                } >> @@ -524,6 +526,7 @@ static int __maybe_unused titsc_resume(struct device *dev) >>                titsc_writel(ts_dev, REG_IRQWAKEUP, >>                                0x00); >>                titsc_writel(ts_dev, REG_IRQCLR, IRQENB_HW_PEN); >> +             pm_relax(ts_dev->mfd_tscadc->dev); >>        } >>        titsc_step_config(ts_dev); >>        titsc_writel(ts_dev, REG_FIFO0THR, >> -- >> 2.17.0 >> > > Thanks. > > -- > Dmitry