Received: by 10.192.165.156 with SMTP id m28csp1148906imm; Mon, 16 Apr 2018 15:08:14 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+fadHXuUsAlaALk5l2WiKcsJdBo2JfInhl+EwLQxnjIgOAzcgjw2HcvL26HLAhA0gg5dXX X-Received: by 10.98.68.86 with SMTP id r83mr23197222pfa.145.1523916494436; Mon, 16 Apr 2018 15:08:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523916494; cv=none; d=google.com; s=arc-20160816; b=0fh94EyU6eu+VYnLsWO/eXWUcy4KZAk21x+qrHBDvGRmOMPnL6OjaX9XgrlXIGfXYJ 1WEIlHeT9ppFOP+Decic3WzkklAP08qmLB/6CofTkQNL7+Ig3D4TFoXoesJ1cyBXDj1f zOvlAq2B4+ufW+51vdVlFMNfHf8HTdL3MOsOrxEHHbPWOMQERuNW613Y4OEdLQ/c1DW5 CNQ72eQW0hJCU2rkFyr1Bb78XA5tq+/nMNnUO4/lROab/EnJHzF+sX8c4ZK0V6NVjs/D ezJmj/ki9UC/4wB9vADve5xMy38RHn2pdgwq7/yzvk0OF5UeD1b/MMo6+J1lAiNnvOwe V4Tw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dmarc-filter :dkim-signature:dkim-signature:arc-authentication-results; bh=SM8SU56fx8BibeUz9syDN0SENTZn65+axqqxSvNdcy0=; b=OP3ltHhn/d3UVx6UE+1vjBQM4cG3emXj+6U9KUhAmjT0BfmwKX0QVTWPRgC3t3pJ3y OK7yg+ZkYCP5jaQygOuTwiyteT8WYuSvGmm4wnFDvj1r+HgwF5e3jdDMVXs4uSROHoX9 jNZOucYpod4D2uPdg31NoupHVVHHwHmj+mQwWk8UNyKvqczAZvqSfCZtxT/nn6IbcZDf DclKFFdLax5F59OmxYl/7PKHAGoAx7W2YODSTo2eoiLg9jAVQz3MNhIyJlsukVHdYMIH GhfGpZ+GnMYubgFi26daDOul+NzTxUTgdR7HD9EY4a7PL066St4+hAPQVBi436VZ+pHd LXPw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=OOAlahFF; dkim=pass header.i=@codeaurora.org header.s=default header.b=mptG+/YY; 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 l192si9174810pge.365.2018.04.16.15.08.00; Mon, 16 Apr 2018 15:08:14 -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=@codeaurora.org header.s=default header.b=OOAlahFF; dkim=pass header.i=@codeaurora.org header.s=default header.b=mptG+/YY; 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 S1753262AbeDPWG5 (ORCPT + 99 others); Mon, 16 Apr 2018 18:06:57 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:50234 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752209AbeDPWGz (ORCPT ); Mon, 16 Apr 2018 18:06:55 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id BDCE860AE0; Mon, 16 Apr 2018 22:06:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1523916414; bh=4Ev2qepjI5EN87sr0lzok5PebBrPa7VFdfcD92PUauk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=OOAlahFF47OeJD6+ZMERTSK347UNgb5BOpwyQ2vOgFw9dj4i+/8p7LslERMEW7ERC AlHJG8k73jvOBXgNkgN5KfkVknp1mfm4UHC9HBfoLUJGfVAAczEqvFxygU0g2nfX8B TpAir7ARZ5r/uReH3d/R8iBEeXSwLg0WNdh+sCno= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from [10.46.164.143] (i-global254.qualcomm.com [199.106.103.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: collinsd@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 5A760600ED; Mon, 16 Apr 2018 22:06:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1523916413; bh=4Ev2qepjI5EN87sr0lzok5PebBrPa7VFdfcD92PUauk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=mptG+/YY5VYX6d8e6mSKRLl4QrdBNNVobPcYBGiTw23Dcn7e718tT+yTmDvliP8BE scymRs3eqWSBqj6eaa+HrxLAPuBFaLNNGJ5NjRGBEcyoMA+jvjv/YmlhaUggcKwU/w pRYGKbhh8gJ6vFf/QvuiGDqD1M1Btwj8oPQ7BMw0= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 5A760600ED Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=collinsd@codeaurora.org Subject: Re: [PATCH v2 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings To: Rob Herring Cc: broonie@kernel.org, lgirdwood@gmail.com, mark.rutland@arm.com, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, rnayak@codeaurora.org, sboyd@kernel.org, dianders@chromium.org References: <39b676d2ba7dac2436196cc5a090c6f151498dc8.1523673467.git.collinsd@codeaurora.org> <20180416205749.556rbkzaja33oref@rob-hp-laptop> From: David Collins Message-ID: Date: Mon, 16 Apr 2018 15:06:52 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20180416205749.556rbkzaja33oref@rob-hp-laptop> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Rob, On 04/16/2018 01:57 PM, Rob Herring wrote: > On Fri, Apr 13, 2018 at 07:50:34PM -0700, David Collins wrote: >> Introduce bindings for RPMh regulator devices found on some >> Qualcomm Technlogies, Inc. SoCs. These devices allow a given >> processor within the SoC to make PMIC regulator requests which >> are aggregated within the RPMh hardware block along with requests >> from other processors in the SoC to determine the final PMIC >> regulator hardware state. >> >> Signed-off-by: David Collins >> --- >> .../bindings/regulator/qcom,rpmh-regulator.txt | 207 +++++++++++++++++++++ >> .../dt-bindings/regulator/qcom,rpmh-regulator.h | 36 ++++ >> [...] >> +++ b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt >> [...] >> +- vdd_s1-supply > > Use '-' rather than '_' on all these. I will change this on the next patch set. >> +- vdd_s2-supply >> +- vdd_s3-supply >> +- vdd_s4-supply >> +- vdd_s5-supply >> +- vdd_s6-supply >> +- vdd_s7-supply >> +- vdd_s8-supply >> +- vdd_s9-supply >> +- vdd_s10-supply >> +- vdd_s11-supply >> +- vdd_s12-supply >> +- vdd_s13-supply >> +- vdd_l1_l27-supply >> +- vdd_l2_l8_l17-supply >> +- vdd_l3_l11-supply >> +- vdd_l4_l5-supply >> +- vdd_l6-supply >> +- vdd_l7_l12_l14_l15-supply >> +- vdd_l9-supply >> +- vdd_l10_l23_l25-supply >> +- vdd_l13_l19_l21-supply >> +- vdd_l16_l28-supply >> +- vdd_l18_l22-supply >> +- vdd_l20_l24-supply >> +- vdd_l26-supply >> +- vdd_lvs1_lvs2-supply >> +- vdd_lvs1_lvs2-supply >> + Usage: optional (PM8998 only) >> + Value type: >> + Definition: phandle of the parent supply regulator of one or more of the >> + regulators for this PMIC. >> + >> +- vdd_bob-supply >> + Usage: optional (PMI8998 only) >> + Value type: >> + Definition: BOB regulator parent supply phandle >> + >> +- vdd_s1-supply >> +- vdd_s2-supply >> +- vdd_s3-supply >> +- vdd_s4-supply > > Listed twice? > >> + Usage: optional (PM8005 only) >> + Value type: >> + Definition: phandle of the parent supply regulator of one or more of the >> + regulators for this PMIC. I listed vdd_s1-supply to vdd_s4-supply here twice because I wanted to group together the supplies supported by each PMIC. PM8005 only supports these 4 regulator supplies. PM8998 supports these 4 along with many others. How else would suggest that I capture this per-PMIC support information? >> +=============================== >> +Second Level Nodes - Regulators >> +=============================== >> + >> +- qcom,regulator-initial-voltage >> + Usage: optional; VRM regulators only >> + Value type: >> + Definition: Specifies the initial voltage in microvolts to request for a >> + VRM regulator. >> + >> +- regulator-initial-mode > > Vendor prefix? No, this does not need a vendor prefix. The regulator-initial-mode property is already defined for all regulator devices [1]: regulator-initial-mode: initial operating mode. The set of possible operating modes depends on the capabilities of every hardware so each device binding documentation explains which values the regulator supports. The values supported by the property are hardware specific and thus must be listed in device specific binding files like this one. Here is a previously merged example: [2]. Thanks, David [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/regulator/regulator.txt?h=v4.17-rc1#n59 [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/regulator/twl-regulator.txt?h=v4.17-rc1#n60 -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project