Received: by 10.192.165.148 with SMTP id m20csp3485627imm; Mon, 30 Apr 2018 00:36:26 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrks2sIsuiRGO76zENmmm79rVcQkNwqyRTx7Z3U0wM4Du+frbBUzYuJEgrFBgP4ZZr4CUpC X-Received: by 2002:a17:902:ab8d:: with SMTP id f13-v6mr10849880plr.81.1525073786465; Mon, 30 Apr 2018 00:36:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525073786; cv=none; d=google.com; s=arc-20160816; b=Gr96KlRIbDr2lrsPtns/62GjB5x28pC1PO8tX3ql76oCJbQpCuX+d/sGvXOnPuqWyM y+HTRzEO8fY9qiJ7dcLuCXzQmZkph0gv9+xEpK4hBmlCsJBZW5vmcakoit5WVofxYjnU OoejmX5kxlyh6NQt/ie6a0uDNrzp9F6yxHqL7djyFTw+YPb3O5LoaDyTHoQZ9gb+49r1 8PyypjdhiJ97IFibpYZIcXQ+vgaiuhVZUPyH6eEKLhhWMmagmJGzt1JoZXfc7f7wkDbq qhelY458YoY9/dK6zdqJR0aZR+ytRDX7RFH0LTrnSVOpwF7o3x2YIdwvxz9v897/cZq6 xZow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=AUmhHh7bFC945/Dk89nQhEZ5Zi5c7EXBJlW+JgiSUMA=; b=XaS3pW6yvt1z49sfpr4RiyNz9yejjf+Dh0WiIKW5/ciL/v8LgnX2uolj/tY+i+rNLU WVZocFN/A2RyLPSs2PuNawj05/bLzUVu7Q6yM+YNyJQn9E5FgVe41iqCnXfjUVHq7GP3 ldRE+v1BXc3CAKCrjioK/U1pYiQ/zf8uKpgvmwAOmFpFrDPSL/QagIgibgoBSdL3Ty5f hKYfP0U/HSCKCIvHUAWXyrJiOAywxWIGyo0KGPXJt0iEKl5XofQLZ23W+izT/DvJIvO5 i5zm+/bbQl1eFN72rRS4x7vlN2Xgt4Y+MCBFjDl9Oov9IHBZFecLAfOtRAfJekJiz8jr xWng== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q28si7091461pfl.317.2018.04.30.00.36.12; Mon, 30 Apr 2018 00:36:26 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752383AbeD3Hea (ORCPT + 99 others); Mon, 30 Apr 2018 03:34:30 -0400 Received: from mailgw02.mediatek.com ([210.61.82.184]:64473 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751917AbeD3He3 (ORCPT ); Mon, 30 Apr 2018 03:34:29 -0400 X-UUID: ab5a952285774b649aab91fb9ac299b3-20180430 Received: from mtkexhb02.mediatek.inc [(172.21.101.103)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 436298445; Mon, 30 Apr 2018 15:34:25 +0800 Received: from mtkcas07.mediatek.inc (172.21.101.84) by mtkmbs08n1.mediatek.inc (172.21.101.55) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 30 Apr 2018 15:34:23 +0800 Received: from [172.21.77.33] (172.21.77.33) by mtkcas07.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1210.3 via Frontend Transport; Mon, 30 Apr 2018 15:34:23 +0800 Message-ID: <1525073663.12322.219.camel@mtkswgap22> Subject: Re: [PATCH v2 01/17] dt-bindings: power: reset: mt6323: add bindings for MT6323 power controller From: Sean Wang To: Rob Herring CC: , , , , , , , , , , , , Date: Mon, 30 Apr 2018 15:34:23 +0800 In-Reply-To: <20180427200225.lq63ex7eiukc6egl@rob-hp-laptop> References: <0b3123e42c8a47e3fa8b21aa2e139e6d3dc69f41.1524646231.git.sean.wang@mediatek.com> <20180427200225.lq63ex7eiukc6egl@rob-hp-laptop> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2018-04-27 at 15:02 -0500, Rob Herring wrote: > On Wed, Apr 25, 2018 at 05:32:27PM +0800, sean.wang@mediatek.com wrote: > > From: Sean Wang > > > > Adding device-tree binding for the power controller which is a tiny > > circuit block present as a part of MT6323 PMIC and is responsible for > > externally powering off or on a remote SoC the PMIC is connected to. > > > > Cc: devicetree@vger.kernel.org > > Signed-off-by: Sean Wang > > --- > > .../bindings/power/reset/mt6323-poweroff.txt | 20 ++++++++++++++++++++ > > 1 file changed, 20 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/power/reset/mt6323-poweroff.txt > > > > diff --git a/Documentation/devicetree/bindings/power/reset/mt6323-poweroff.txt b/Documentation/devicetree/bindings/power/reset/mt6323-poweroff.txt > > new file mode 100644 > > index 0000000..6f7c590 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/power/reset/mt6323-poweroff.txt > > @@ -0,0 +1,20 @@ > > +Device Tree Bindings for Power Controller on MediaTek PMIC > > + > > +The power controller which could be found on PMIC is responsible for externally > > +powering off or on the remote MediaTek SoC through the circuit BBPU. > > + > > +Required properties: > > +- compatible: Should be one of follows > > + "mediatek,mt6323-pwrc": for MT6323 PMIC > > + > > +Example: > > + > > + pmic { > > + compatible = "mediatek,mt6323"; > > + > > + ... > > + > > + power-controller { > > + compatible = "mediatek,mt6323-pwrc"; > > Why do you need this in DT? It doesn't define any resources. The parent > can just as well register a reset or poweroff handler. > > Rob > Yes, those binding can be removed. I tend to use platform_device_register_data embedded in mfd driver to probe the existent poweroff driver in the next version. > > + }; > > + } > > -- > > 2.7.4 > >