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 1/3] Input: ti_am335x_tsc - Mark IRQ as wakeup capable
Date: Mon, 16 Apr 2018 10:45:42 -0700 [thread overview]
Message-ID: <20180416174542.GB77055@dtor-ws> (raw)
In-Reply-To: <20180414095153.32060-2-vigneshr@ti.com>
On Sat, Apr 14, 2018 at 03:21:51PM +0530, Vignesh R wrote:
> On AM335x, ti_am335x_tsc can wake up the system from suspend, mark the
> IRQ as wakeup capable, so that device irq is not disabled during system
> suspend.
>
> Signed-off-by: Vignesh R <vigneshr@ti.com>
> ---
>
> v2: No changes
>
> drivers/input/touchscreen/ti_am335x_tsc.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/input/touchscreen/ti_am335x_tsc.c b/drivers/input/touchscreen/ti_am335x_tsc.c
> index f1043ae71dcc..810e05c9c4f5 100644
> --- a/drivers/input/touchscreen/ti_am335x_tsc.c
> +++ b/drivers/input/touchscreen/ti_am335x_tsc.c
> @@ -27,6 +27,7 @@
> #include <linux/of.h>
> #include <linux/of_device.h>
> #include <linux/sort.h>
> +#include <linux/pm_wakeirq.h>
>
> #include <linux/mfd/ti_am335x_tscadc.h>
>
> @@ -432,6 +433,12 @@ static int titsc_probe(struct platform_device *pdev)
> goto err_free_mem;
> }
>
> + if (device_may_wakeup(tscadc_dev->dev)) {
> + err = dev_pm_set_wake_irq(tscadc_dev->dev, ts_dev->irq);
Hmm, most of the drivers simply use enable_irq_wake()/disable_irq_wake()
in suspend/resume paths and use dev_pm_set_wake_irq() only for dedicated
and distinct wake interrupts. Why do we not follow the same pattern
here?
Thanks.
> + if (err)
> + dev_err(&pdev->dev, "irq wake enable failed.\n");
> + }
> +
> titsc_writel(ts_dev, REG_IRQENABLE, IRQENB_FIFO0THRES);
> titsc_writel(ts_dev, REG_IRQENABLE, IRQENB_EOS);
> err = titsc_config_wires(ts_dev);
> @@ -462,6 +469,7 @@ static int titsc_probe(struct platform_device *pdev)
> return 0;
>
> err_free_irq:
> + dev_pm_clear_wake_irq(tscadc_dev->dev);
> free_irq(ts_dev->irq, ts_dev);
> err_free_mem:
> input_free_device(input_dev);
> @@ -474,6 +482,7 @@ static int titsc_remove(struct platform_device *pdev)
> struct titsc *ts_dev = platform_get_drvdata(pdev);
> u32 steps;
>
> + dev_pm_clear_wake_irq(ts_dev->mfd_tscadc->dev);
> free_irq(ts_dev->irq, ts_dev);
>
> /* total steps followed by the enable mask */
> --
> 2.17.0
>
--
Dmitry
next prev parent reply other threads:[~2018-04-16 17:45 UTC|newest]
Thread overview: 14+ 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 ` Vignesh R
2018-04-14 9:51 ` [PATCH v2 1/3] Input: ti_am335x_tsc - Mark IRQ as wakeup capable Vignesh R
2018-04-14 9:51 ` Vignesh R
2018-04-16 17:45 ` Dmitry Torokhov [this message]
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-14 9:51 ` 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-14 9:51 ` Vignesh R
2018-04-16 18:01 ` Dmitry Torokhov
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=20180416174542.GB77055@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.