| Message ID | 20180630103318.25355-2-vigneshr@ti.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Sat, 30 Jun 2018, Vignesh R wrote: > Currently tscadc MFD is marked as wakeup capable which incorrect > because, its actually touch event by child TSC device that wakes up the > system. Therefore, remove device_init_wakeup() call that marks TSCADC > device as wakeup capable in favor of moving to mark TSC input device as > wakeup capable later. > > Signed-off-by: Vignesh R <vigneshr@ti.com> > --- > drivers/mfd/ti_am335x_tscadc.c | 1 - > 1 file changed, 1 deletion(-) For my own reference: Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
On Sat, 30 Jun 2018, Vignesh R wrote: > Currently tscadc MFD is marked as wakeup capable which incorrect > because, its actually touch event by child TSC device that wakes up the > system. Therefore, remove device_init_wakeup() call that marks TSCADC > device as wakeup capable in favor of moving to mark TSC input device as > wakeup capable later. > > Signed-off-by: Vignesh R <vigneshr@ti.com> > --- > drivers/mfd/ti_am335x_tscadc.c | 1 - > 1 file changed, 1 deletion(-) Applied, thanks.
diff --git a/drivers/mfd/ti_am335x_tscadc.c b/drivers/mfd/ti_am335x_tscadc.c index 47012c0899cd..858c1a071a81 100644 --- a/drivers/mfd/ti_am335x_tscadc.c +++ b/drivers/mfd/ti_am335x_tscadc.c @@ -270,7 +270,6 @@ static int ti_tscadc_probe(struct platform_device *pdev) if (err < 0) goto err_disable_clk; - device_init_wakeup(&pdev->dev, true); platform_set_drvdata(pdev, tscadc); return 0;
Currently tscadc MFD is marked as wakeup capable which incorrect because, its actually touch event by child TSC device that wakes up the system. Therefore, remove device_init_wakeup() call that marks TSCADC device as wakeup capable in favor of moving to mark TSC input device as wakeup capable later. Signed-off-by: Vignesh R <vigneshr@ti.com> --- drivers/mfd/ti_am335x_tscadc.c | 1 - 1 file changed, 1 deletion(-)