Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp3551836pxx; Mon, 2 Nov 2020 11:55:25 -0800 (PST) X-Google-Smtp-Source: ABdhPJyNPb5ytSay6bPbjbSPSP/6KWHoQT8T0Tl1ru1rDakACM9K+r/BuJDg7V/7QB+zxuh+eYZh X-Received: by 2002:a17:906:ce5c:: with SMTP id se28mr15743966ejb.365.1604346924987; Mon, 02 Nov 2020 11:55:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604346924; cv=none; d=google.com; s=arc-20160816; b=M/4C1xaKIQd5PzbPC+aaBTa3i44qziAT5Sg5B7Y7qx2QP/vehwXNTv0TZ0BQvAVWla aBSUyFB17Yr+Y4ZpS2HK4tkAiYHXB20MLRp3EzJXTnm9YgZK4M+aKr3Ld9jKZkgruDet URnQrWJx4nWPOHk1GDZvU5Rkg7zxKdUy0Qgdl64uak0tk/zaFmdXkQpa79OmvhUs+Grt wftmxMxEk+/pqViNfqE/DxW0qUa2u6KlM6KA61nxx/2R0gzYvPecUpn9AkAJDGjrm+WO iCi09CVlhq1eNMI2BKrRfGtxzolIb0x/+46U8/33WMY+YKK3XENlWO9xUIA9N388zQs8 i4Dg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=4dBt713rLDEfHGPmeT5DITAyHmvIlr+ovXDsXZnt4Bg=; b=eysCCZ269OB5uy/LH5Wq+NUeroMklwoow9OEDIWY6OVJAUhLN6Ilnf01NeA/Tf7VRV gd5Lmy1OTOU6fx4ANtrysCVipOwSd+p4JBm3z7tEtlzgF+5Syp5cUKeynKqUEDo0R+bC GUi8BFz7jRVd485V3EQm6jUb2nslSgCObqr73MbY2DtPQCD1JO/AkPmG417h+6l4PpI3 kBgQvyqkZBAfo5qXlil67+KZ0PfUZqFv7J2u4TInHSmoAzf4kiPF9jLuiR3fH54gZ7e4 rBWtqPo4tQEzjgOr7D/AAJMVADONapTZpWRIA4bTQs6iHUAWz9rKFjcteDke9f04htA9 FrrQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u13si10140125ejt.298.2020.11.02.11.55.02; Mon, 02 Nov 2020 11:55:24 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727118AbgKBTwl (ORCPT + 99 others); Mon, 2 Nov 2020 14:52:41 -0500 Received: from alexa-out-sd-01.qualcomm.com ([199.106.114.38]:35465 "EHLO alexa-out-sd-01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727085AbgKBTwk (ORCPT ); Mon, 2 Nov 2020 14:52:40 -0500 Received: from unknown (HELO ironmsg01-sd.qualcomm.com) ([10.53.140.141]) by alexa-out-sd-01.qualcomm.com with ESMTP; 02 Nov 2020 11:52:39 -0800 X-QCInternal: smtphost Received: from gurus-linux.qualcomm.com ([10.46.162.81]) by ironmsg01-sd.qualcomm.com with ESMTP; 02 Nov 2020 11:52:39 -0800 Received: by gurus-linux.qualcomm.com (Postfix, from userid 383780) id 11736188E; Mon, 2 Nov 2020 11:52:39 -0800 (PST) Date: Mon, 2 Nov 2020 11:52:39 -0800 From: Guru Das Srinagesh To: Rob Herring Cc: Mark Brown , Markus Elfring , Lee Jones , Bjorn Andersson , Greg KH , Guenter Roeck , Joe Perches , Subbaraman Narayanamurthy , David Collins , Anirudh Ghayal , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH v2 2/3] dt-bindings: mfd: Add QCOM PM8008 MFD bindings Message-ID: <20201102195238.GB29492@codeaurora.org> References: <20201030154900.GA3896697@bogus> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201030154900.GA3896697@bogus> User-Agent: Mutt/1.5.24 (2015-08-30) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 30, 2020 at 10:49:00AM -0500, Rob Herring wrote: > On Thu, Oct 22, 2020 at 02:35:41PM -0700, Guru Das Srinagesh wrote: > > Add device tree bindings for the driver for Qualcomm Technology Inc.'s > > PM8008 MFD PMIC. > > > > Signed-off-by: Guru Das Srinagesh > > --- > > .../bindings/mfd/qcom,pm8008-irqchip.yaml | 102 +++++++++++++++++++++ > > 1 file changed, 102 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/mfd/qcom,pm8008-irqchip.yaml > > > > diff --git a/Documentation/devicetree/bindings/mfd/qcom,pm8008-irqchip.yaml b/Documentation/devicetree/bindings/mfd/qcom,pm8008-irqchip.yaml > > new file mode 100644 > > index 0000000..31d7b68 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/mfd/qcom,pm8008-irqchip.yaml > > @@ -0,0 +1,102 @@ > > +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/mfd/qcom,pm8008-irqchip.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Qualcomm Technologies, Inc. PM8008 Multi-Function Device PMIC > > + > > +maintainers: > > + - Guru Das Srinagesh > > + > > +description: | > > + PM8008 is a PMIC that contains 7 LDOs, 2 GPIOs, temperature monitoring, and > > + can be interfaced over I2C. > > No bindings for all those functions? Bindings should be complete. While pushing out this patchset, I accidentally dropped the "RFC" tag in the mail subjects. This driver and binding document are meant to be just an exemplar for how the framework changes would be used, and hence I felt adding only a single node would suffice for illustration purposes. > > > + > > +properties: > > + compatible: > > + items: > > + - const: qcom,pm8008-irqchip > > Why irqchip? Since the driver's main functions are to register with the regmap-irq framework and to pass a regmap to the child nodes it populates. Would "qcom,pm8008-mfd" be more appropriate? > > > + > > + reg: > > + maxItems: 1 > > + > > + interrupt-names: > > + items: > > + - const: pm8008 > > + > > + interrupts: > > + maxItems: 1 > > + > > + interrupt-controller: true > > + > > + "#address-cells": > > + const: 1 > > + description: Must be specified if child nodes are specified. > > + > > + "#size-cells": > > + const: 0 > > + description: Must be specified if child nodes are specified. > > + > > + "#interrupt-cells": > > + const: 2 > > + description: | > > + The first cell is the IRQ number, the second cell is the IRQ trigger flag. > > + > > +patternProperties: > > + "^.*@[0-9a-f]+$": > > '^.*' can be dropped. That's redundant. Done. > > > + type: object > > + # Each peripheral in PM8008 must be represented as a child node with an > > + # optional label for referencing as phandle elsewhere. This is optional. > > + properties: > > + compatible: > > + description: The compatible string for the peripheral's driver. > > + > > + reg: > > + maxItems: 1 > > What does the address represent? It's non-standard, so it needs to be > defined. Will add description. > > > + > > + interrupts: > > + maxItems: 1 > > + > > + required: > > + - compatible > > + - reg > > + - interrupts > > + > > +required: > > + - compatible > > + - reg > > + - interrupts > > + - "#interrupt-cells" > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + #include > > + qupv3_se13_i2c { > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + pm8008i@8 { > > + compatible = "qcom,pm8008-irqchip"; > > + reg = <0x8>; > > + #address-cells = <1>; > > + #size-cells = <0>; > > + interrupt-controller; > > + #interrupt-cells = <2>; > > + > > + interrupt-names = "pm8008"; > > + interrupt-parent = <&tlmm>; > > + interrupts = <32 IRQ_TYPE_EDGE_RISING>; > > + > > + pm8008_tz: qcom,temp-alarm@2400 { > > Must be documented. > > And don't use vendor prefixes in node names. Done. > > > + compatible = "qcom,spmi-temp-alarm"; > > + reg = <0x2400>; > > + interrupts = <0x5 IRQ_TYPE_EDGE_BOTH>; > > + #thermal-sensor-cells = <0>; > > + }; > > + }; > > + }; > > + > > +... > > -- > > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, > > a Linux Foundation Collaborative Project > >