Received: by 10.213.65.68 with SMTP id h4csp625178imn; Fri, 23 Mar 2018 11:57:00 -0700 (PDT) X-Google-Smtp-Source: AG47ELshSvTfjTu2sbAz7J6AIDBw35Yd1SRlGk+0m0W+oXH2/rDObj0uu+yOONtj1mOGyAIHx22E X-Received: by 2002:a17:902:30f:: with SMTP id 15-v6mr29672104pld.365.1521831419989; Fri, 23 Mar 2018 11:56:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521831419; cv=none; d=google.com; s=arc-20160816; b=pUYg1xzgdNBlceGiZw3LL2Xa1Lwxf+a/soDAp2GszJFIFxwVO0sCNIyc/UT02/d1zK bzUqXHGXbi/67ByAbcbB9MH8ql4l2kOMxUJPubOBj/Yd1H9zPzrMBi33Hhd7nH7HankS /n5NagUBpaRAHIKgcsIKnCqlGPQE3QOvGhLWBZPs7rjUrGMXtKDLc6V2PYxMxB6YDg3N c/sb2dCfUjR6mjtcpvLNt4R1pO7ylmY4toK3X/GIdvSgODaM8E8rKR1LIZhcnGgt4sny y/trBUr06qLK8Hjn6tzMNpaupOmolQymAis9mDi9N7EfJiAVS3jkc09lrZ55z3px8dwG z6sA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=vYpPYbV3U0tJiWhWcgEPQbKcH8T8GEGLYSpWlm8OJj0=; b=xcFbNDg2LG6wTc4Gk8SXD4MYbkZd5+ib0OyuW3s+3shP67fuGRSxLoADVDCIn/TBU5 12VTkFEN0TxuJYcdu1J+zP28eOd4bN0DPLZFRLwv+TBxIQFvVT7vW/cCufjSy+J+PqSV boD8kmpAyDqUm3Ki8eo+BfihCsP1R+dohYbx0qxvSdyh6xsJcelgewu1alsTCraN6eyl P31JXcARZpTCqvXqyfw/pYVQUcroM2yVH4BLzYgAR3jf+gG/gSMyiYcFgX0sx1y9Z86j Dzgcxgl2zo3fxmlbhSprjWRNDWt4Q+AVJsKdMCIbF2DlJpkCPlvsghx7NRNhmy3s+6R4 Ej1Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=kqeZU+VH; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h13si7197485pfh.182.2018.03.23.11.56.45; Fri, 23 Mar 2018 11:56:59 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=kqeZU+VH; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752579AbeCWSy2 (ORCPT + 99 others); Fri, 23 Mar 2018 14:54:28 -0400 Received: from mail-pg0-f66.google.com ([74.125.83.66]:34683 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752563AbeCWSyX (ORCPT ); Fri, 23 Mar 2018 14:54:23 -0400 Received: by mail-pg0-f66.google.com with SMTP id m15so4923793pgc.1; Fri, 23 Mar 2018 11:54:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=vYpPYbV3U0tJiWhWcgEPQbKcH8T8GEGLYSpWlm8OJj0=; b=kqeZU+VHyN1bro8hv3CNDpJGoF+ZhuAHQr72pbbgKexyPY0n35CV7d1IxeT/2z84xp BEddodlhAa8Ag7juOGFPSPuxLZFRv9qLv000KYbuxKJPDHJsMtDH7U+9p5WYWR0vM9Sl Nxm8ZBeCG5u2Iv3GVr7xEjxBoKZk6NPpy0KqpT8Lv1f3zeq/fV3xtuYCAwte8BSuayE0 iRFxAX/DX8d2W7CApwsEC4/Qxk7fNGh4R5CjBplCdD5UWIXrKhXWiHJfdlI9p/Ds9Qoj Kza+yl0RqN3grkwv+wbq4YgReZAATXuQwE/2pu6Yxf+2NIX8Qf3U3Oi7mNeetifeGvu+ LV5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=vYpPYbV3U0tJiWhWcgEPQbKcH8T8GEGLYSpWlm8OJj0=; b=WlJ6TA171PtG41C7Bkr+aLm3htf/IK5HRa7jd7KkPo3CO8OX0weeerbO6rjEmEcC/e cLcp09XgBHCJdA+l2YCo2pO+PRdOXTMdGx2c2HV/Uxjznmn+RG3/M4NgKJkqRsZSLUe3 QRqDFn4t8uUA5jZnXDkoS8mI72iLxDzJtnzPRqNtEGpdtYV1+KhmKIVNmsrhFvZABIKH aCOqjkylVPvQBiEXhZgjdUrrLQ6SQJzNA2NcAHQE4iJm5hT0eyp2HWJDSVsQSeikBSOe K/HNFAVHV6zx+5VjT8PHKe0PGF3KzUxYFEz6ObL6kkS0hBeLOdqH8+Uf6kPjkztWpGYR Ugsw== X-Gm-Message-State: AElRT7F/aMmFoiwJLBNwkFZgRKlon2avHXZWzWgmoL02+SmvnRo4jQan HAoSQiyl7JugGb5xsUbI/dI= X-Received: by 10.98.246.26 with SMTP id x26mr8203264pfh.81.1521831261637; Fri, 23 Mar 2018 11:54:21 -0700 (PDT) Received: from dtor-ws ([2620:0:1000:1511:8de6:27a8:ed13:2ef5]) by smtp.gmail.com with ESMTPSA id y15sm593854pfb.37.2018.03.23.11.54.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 23 Mar 2018 11:54:20 -0700 (PDT) Date: Fri, 23 Mar 2018 11:54:18 -0700 From: Dmitry Torokhov To: Sean Wang Cc: Rob Herring , Lee Jones , Alexandre Belloni , Mark Rutland , a.zummo@towertech.it, devicetree@vger.kernel.org, linus.walleij@linaro.org, jcsing.lee@samsung.com, linux-kernel@vger.kernel.org, krzk@kernel.org, javier@osg.samsung.com, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-input@vger.kernel.org, matthias.bgg@gmail.com, eddie.huang@mediatek.com, Chen.Zhong@mediatek.com, beomho.seo@samsung.com, linux-rtc@vger.kernel.org Subject: Re: [PATCH v6 0/6] Add MediaTek PMIC keys support Message-ID: <20180323185418.GD255819@dtor-ws> References: <1508937364-30054-1-git-send-email-chen.zhong@mediatek.com> <808b2029da224ab687fb0553cbc1c68e@mtkmbs08n1.mediatek.inc> <1521685073.28226.10.camel@mtkswgap22> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1521685073.28226.10.camel@mtkswgap22> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Sean, On Thu, Mar 22, 2018 at 10:17:53AM +0800, Sean Wang wrote: > Hi, Dmitry and Lee > > The series seems not being got merged. Are they good enough to be ready > into the your tree? > > Recently I've tested the series with focusing on pwrkey event generated > through interrupt when push and release the key on bpi-r2 board and then > finally it's working fine. but for homekey it cannot be found on the > board and thus I cannot have more tests more about it. > > Tested-by: Sean Wang You have my Ack on the input patch; I expect it go through Lee's tree as there are some dependencies on mfd core piece. Thanks. > > Sean > > > On Thu, 2018-03-22 at 10:03 +0800, Sean Wang (王志亘) wrote: > > > > > -----Original Message----- > > > From: Linux-mediatek [mailto:linux-mediatek-bounces@lists.infradead.org] On > > > Behalf Of Chen Zhong > > > Sent: Wednesday, October 25, 2017 9:16 PM > > > To: Dmitry Torokhov ; Rob Herring > > > ; Lee Jones ; Alexandre Belloni > > > > > > Cc: Mark Rutland ; Alessandro Zummo > > > ; devicetree@vger.kernel.org; Linus Walleij > > > ; Jaechul Lee ; linux- > > > kernel@vger.kernel.org; Krzysztof Kozlowski ; Javier > > > Martinez Canillas ; linux- > > > mediatek@lists.infradead.org; linux-arm-kernel@lists.infradead.org; linux- > > > input@vger.kernel.org; Matthias Brugger ; Eddie > > > Huang (S智) ; Chen Zhong (钟辰) > > > ; Beomho Seo ; > > > linux-rtc@vger.kernel.org > > > Subject: [PATCH v6 0/6] Add MediaTek PMIC keys support > > > > > > MediaTek PMIC are multi-function devices that can handle key interrupts, > > > typically there are two keys attached to PMIC, which called pwrkey and > > > homekey. PWRKEY usually used to wake up system from sleep. Homekey can > > > used as volume down key due to board design. Long press keys can shutdown > > > PMIC, the mode can be choose to be one key only or two keys together. > > > This series add support for key functions for MediaTek PMIC MT6397/MT6323. > > > > > > Changes since v5: > > > - use __maybe_unused annotation instead of #ifdef guard > > > - use of_* API instead of device_* API > > > > > > Changes since v4: > > > - rebase to Linux 4.14-rc1 > > > - add a common keyboard binding document > > > - use child device tree node to define each key > > > > > > Changes since v3: > > > - make the naming to be consistent as mtk_pmic or MTK_PMIC > > > - add suspend/resume functions to enable/disable irq > > > - change binding properties to define wakeup sources > > > > > > Changes since v2: > > > - use standard properties for keycodes and debounce time > > > - change to use platform_get_irq in leaf drivers > > > - use better ways to define IRQ resources > > > > > > Changes since v1: > > > - create irq mappings in mfd core driver instead of leaf drivers > > > - remove some unused parts in mtk-pmic-keys driver > > > > > > Chen Zhong (6): > > > mfd: mt6397: create irq mappings in mfd core driver > > > dt-bindings: input: Add common keyboard document bindings > > > dt-bindings: input: Add document bindings for mtk-pmic-keys > > > dt-bindings: mfd: Add bindings for the keys as subnode of PMIC > > > input: Add MediaTek PMIC keys support > > > mfd: mt6397: Add PMIC keys support to MT6397 driver > > > > > > Documentation/devicetree/bindings/input/keys.txt | 8 + > > > .../devicetree/bindings/input/mtk-pmic-keys.txt | 43 +++ > > > Documentation/devicetree/bindings/mfd/mt6397.txt | 6 + > > > drivers/input/keyboard/Kconfig | 9 + > > > drivers/input/keyboard/Makefile | 1 + > > > drivers/input/keyboard/mtk-pmic-keys.c | 339 > > > +++++++++++++++++++++ > > > drivers/mfd/mt6397-core.c | 26 +- > > > drivers/rtc/rtc-mt6397.c | 7 +- > > > 8 files changed, 432 insertions(+), 7 deletions(-) create mode 100644 > > > Documentation/devicetree/bindings/input/keys.txt > > > create mode 100644 Documentation/devicetree/bindings/input/mtk-pmic- > > > keys.txt > > > create mode 100644 drivers/input/keyboard/mtk-pmic-keys.c > > > > > > -- > > > 1.9.1 > > > > > > > > > > > > _______________________________________________ > > > Linux-mediatek mailing list > > > Linux-mediatek@lists.infradead.org > > > http://lists.infradead.org/mailman/listinfo/linux-mediatek > > -- Dmitry