From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,T_DKIMWL_WL_HIGH,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B9222ECDE5F for ; Sat, 21 Jul 2018 18:10:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6620520868 for ; Sat, 21 Jul 2018 18:10:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="IiGpSdBW" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6620520868 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728388AbeGUTDe (ORCPT ); Sat, 21 Jul 2018 15:03:34 -0400 Received: from mail.kernel.org ([198.145.29.99]:54560 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728083AbeGUTDe (ORCPT ); Sat, 21 Jul 2018 15:03:34 -0400 Received: from archlinux (cpc91196-cmbg18-2-0-cust659.5-4.cable.virginm.net [81.96.234.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A90DB20868; Sat, 21 Jul 2018 18:09:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1532196598; bh=RUmVNor4t99ruwYaObefrkA/XVpr63mj2pA9dqgeJOc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=IiGpSdBWbFphnS3q0tZ9vu8S8qY+6SWcY9wfzIkSQAitxgzOFcxQ60UHRq7xTAS6b VU4zxDAQIrBsHoUjUjkP3AKaK+gMhd6uJaeMh/ufPGOcPwxSnGCZFF00XF5bBev5ZZ PHnGgA7zUPrwsHtJAVEOkdDEqyDCqQ0Y0YHRd6SY= Date: Sat, 21 Jul 2018 19:09:54 +0100 From: Jonathan Cameron To: Dmitry Torokhov Cc: Lee Jones , Vignesh R , linux-iio@vger.kernel.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-input@vger.kernel.org Subject: Re: [PATCH 0/5] ti_am335x_tsc: Enable wakeup capability Message-ID: <20180721190954.3d08e774@archlinux> In-Reply-To: <20180718170902.vk7rahyoaevucxbi@penguin> References: <20180630103318.25355-1-vigneshr@ti.com> <20180718074736.GA4641@dell> <20180718170902.vk7rahyoaevucxbi@penguin> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 18 Jul 2018 17:09:02 +0000 Dmitry Torokhov wrote: > On Wed, Jul 18, 2018 at 08:47:36AM +0100, Lee Jones wrote: > > On Tue, 17 Jul 2018, Vignesh R wrote: > > > > > Hi Dmitry, > > > > > > On Saturday 30 June 2018 04:03 PM, Vignesh R wrote: > > > > On AM335x, resistive TSC can wakeup the system from low power state. > > > > Currently, parent MFD device is marked as wakeup source, which is > > > > inaccurate as its the touch event generated by TSC thats the wakeup > > > > source. This series moves all wakeup related calls to operate on TSC > > > > device instead of MFD. It also marks TSC IRQ as wakeup capable, so that > > > > its not disabled during system suspend. > > > > > > > > This series is based on Dmitry's comments here: > > > > https://lkml.org/lkml/2018/4/24/65 > > > > > > > > There are many new patches in this series, hence did not mark this as v4. > > > > > > > > Vignesh R (5): > > > > mfd: ti_am335x_tscadc: Don't mark TSCADC MFD as wakeup capable > > > > Input: ti_am335x_tsc: Mark TSC device as wakeup source > > > > mfd: ti_am335x_tscadc: Keep ADC interface on if child is wakeup > > > > capable > > > > iio: adc: ti_am335x_adc: Disable ADC during suspend unconditionally > > > > Input: ti_am335x_tsc: Mark IRQ as wakeup capable > > > > > > > > drivers/iio/adc/ti_am335x_adc.c | 12 ++++-------- > > > > drivers/input/touchscreen/ti_am335x_tsc.c | 22 +++++++++++++++++----- > > > > drivers/mfd/ti_am335x_tscadc.c | 14 +++++++++++++- > > > > 3 files changed, 34 insertions(+), 14 deletions(-) > > > > > > > > > > Gentle ping... Could you review/pick this series? MFD amd IIO bits are > > > already ACKed > > > > MFD patches are reviewed "for my own reference" meaning that we > > haven't yet agreed on a merge plan yet. > > I think this series makes sense to be pushed through a single tree as > opposed to being spread between 3, even if it could technically be > possible. It looks like Jonathan is fine with going it through either > his or some other tree, I am fine with it going through MFD. I just > Acked the 2 input-related patches. Just to confirm, MFD is fine for iio patches. That driver isn't a hotbed of activity ;) Jonathan > > Thanks. >