From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f193.google.com ([209.85.128.193]:34845 "EHLO mail-wr0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932412AbeGDHiO (ORCPT ); Wed, 4 Jul 2018 03:38:14 -0400 Received: by mail-wr0-f193.google.com with SMTP id h40-v6so4255190wrh.2 for ; Wed, 04 Jul 2018 00:38:13 -0700 (PDT) Date: Wed, 4 Jul 2018 08:38:10 +0100 From: Lee Jones To: Vignesh R Cc: Jonathan Cameron , Dmitry Torokhov , linux-iio@vger.kernel.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-input@vger.kernel.org Subject: Re: [PATCH 1/5] mfd: ti_am335x_tscadc: Don't mark TSCADC MFD as wakeup capable Message-ID: <20180704073810.GL20176@dell> References: <20180630103318.25355-1-vigneshr@ti.com> <20180630103318.25355-2-vigneshr@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <20180630103318.25355-2-vigneshr@ti.com> Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.kernel.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 > --- > 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 Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog