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=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, 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 B9189ECDFB8 for ; Tue, 24 Jul 2018 17:32:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7541C20883 for ; Tue, 24 Jul 2018 17:32:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="Oo7BWD2w" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7541C20883 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=ti.com 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 S2388631AbeGXSkK (ORCPT ); Tue, 24 Jul 2018 14:40:10 -0400 Received: from fllv0016.ext.ti.com ([198.47.19.142]:34572 "EHLO fllv0016.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388408AbeGXSkK (ORCPT ); Tue, 24 Jul 2018 14:40:10 -0400 Received: from dlelxv90.itg.ti.com ([172.17.2.17]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id w6OHWbWR014457; Tue, 24 Jul 2018 12:32:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1532453557; bh=gF8QzFGGNWOc8qkZ0hphWrHwUrV8QNZ151Hjffzh/5c=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=Oo7BWD2woIeSjilACbYRl4yBn8MHYFouGUHjx7Qfy4Sv9vwCb+Q5ByldSibTfmAjR rSomtypIitaOUq8Tg18+7lUdFLCAZgJYGka6r//kYMArAsaRXLKpp4MWAP1VhbqSZv Mo/Ei3ZfFXAyzhfAzRKy35C0Evw94z4k1ZjlTjTg= Received: from DLEE112.ent.ti.com (dlee112.ent.ti.com [157.170.170.23]) by dlelxv90.itg.ti.com (8.14.3/8.13.8) with ESMTP id w6OHWam2013073; Tue, 24 Jul 2018 12:32:36 -0500 Received: from DLEE105.ent.ti.com (157.170.170.35) by DLEE112.ent.ti.com (157.170.170.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 24 Jul 2018 12:32:36 -0500 Received: from dlep33.itg.ti.com (157.170.170.75) by DLEE105.ent.ti.com (157.170.170.35) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1466.3 via Frontend Transport; Tue, 24 Jul 2018 12:32:36 -0500 Received: from [172.24.190.89] (ileax41-snat.itg.ti.com [10.172.224.153]) by dlep33.itg.ti.com (8.14.3/8.13.8) with ESMTP id w6OHWXUT000858; Tue, 24 Jul 2018 12:32:34 -0500 Subject: Re: [PATCH 0/5] ti_am335x_tsc: Enable wakeup capability To: Lee Jones , Dmitry Torokhov CC: Jonathan Cameron , , , , References: <20180630103318.25355-1-vigneshr@ti.com> <20180718074736.GA4641@dell> <20180718170902.vk7rahyoaevucxbi@penguin> <20180723053708.GA4213@dell> From: Vignesh R Message-ID: <2236aa96-ca56-fa30-157d-2f484c6968cc@ti.com> Date: Tue, 24 Jul 2018 23:03:30 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180723053708.GA4213@dell> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 23 July 2018 11:07 AM, Lee Jones wrote: > On Wed, 18 Jul 2018, 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'm happy either way. > Thanks Dmitry, Jonathan and Lee Jones! Could this be applied to one of the trees now? MFD perhaps? -- Regards Vignesh