LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com> To: Vignesh R <vigneshr@ti.com> Cc: Grygorii Strashko <grygorii.strashko@ti.com>, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com> Subject: Re: [PATCH v2 3/3] Input: ti_am335x_tsc - Prevent system suspend when TSC is in use Date: Mon, 16 Apr 2018 11:01:48 -0700 [thread overview] Message-ID: <20180416180148.GD77055@dtor-ws> (raw) In-Reply-To: <20180414095153.32060-4-vigneshr@ti.com> On Sat, Apr 14, 2018 at 03:21:53PM +0530, Vignesh R wrote: > From: Grygorii Strashko <grygorii.strashko@ti.com> > > 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. > > Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com> > Signed-off-by: Vignesh R <vigneshr@ti.com> > --- > > 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
next prev parent reply other threads:[~2018-04-16 18:01 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-14 9:51 [PATCH v2 0/3] ti_am335x_tsc: Fix suspend/resume Vignesh R 2018-04-14 9:51 ` [PATCH v2 1/3] Input: ti_am335x_tsc - Mark IRQ as wakeup capable Vignesh R 2018-04-16 17:45 ` Dmitry Torokhov 2018-04-17 8:20 ` Vignesh R 2018-04-14 9:51 ` [PATCH v2 2/3] Input: ti_am335x_tsc - Ack pending IRQs at probe and before suspend Vignesh R 2018-04-16 17:59 ` Dmitry Torokhov 2018-04-17 8:19 ` Vignesh R 2018-04-14 9:51 ` [PATCH v2 3/3] Input: ti_am335x_tsc - Prevent system suspend when TSC is in use Vignesh R 2018-04-16 18:01 ` Dmitry Torokhov [this message] 2018-04-17 8:19 ` Vignesh R
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=20180416180148.GD77055@dtor-ws \ --to=dmitry.torokhov@gmail.com \ --cc=grygorii.strashko@ti.com \ --cc=linux-input@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=tony@atomide.com \ --cc=vigneshr@ti.com \ /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: linkBe 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; as well as URLs for NNTP newsgroup(s).