From patchwork Tue Oct 4 11:56:43 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Viresh Kumar X-Patchwork-Id: 77250 Delivered-To: patch@linaro.org Received: by 10.140.106.72 with SMTP id d66csp2173461qgf; Tue, 4 Oct 2016 04:57:17 -0700 (PDT) X-Received: by 10.67.5.136 with SMTP id cm8mr4389476pad.127.1475582237496; Tue, 04 Oct 2016 04:57:17 -0700 (PDT) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s5si3281996paw.9.2016.10.04.04.57.17; Tue, 04 Oct 2016 04:57:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-pm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@linaro.org; spf=pass (google.com: best guess record for domain of linux-pm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-pm-owner@vger.kernel.org; dmarc=fail (p=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753372AbcJDL5H (ORCPT + 14 others); Tue, 4 Oct 2016 07:57:07 -0400 Received: from mail-pa0-f54.google.com ([209.85.220.54]:34523 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751647AbcJDL5F (ORCPT ); Tue, 4 Oct 2016 07:57:05 -0400 Received: by mail-pa0-f54.google.com with SMTP id rz1so17380589pab.1 for ; Tue, 04 Oct 2016 04:57:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :in-reply-to:references; bh=L5poqbgEGF+2A+MzLzRm1Neo3gmMebVbAfGZ30Al1mM=; b=RyKWJoRbvGofWVGbk5ItvsIZ0Rz1KpvKrjPySMZ4TjfHCWhJE/9aHnGVZk5w26jA2D ewrO7CQbY/KMSuV2jhrPIZPpxHBul9qg6I0ePtWNtLmSi2qWuyl57dbxekuKLBIQ/BCa AexJj1RHv9zC1xoVWiWtdXWlFI+BH9evEYS/w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:in-reply-to:references; bh=L5poqbgEGF+2A+MzLzRm1Neo3gmMebVbAfGZ30Al1mM=; b=T8bbj5Az7TTM+o4dVWgI0PC9JQ1Wjb8u1fsAoOeaMBunH2SkZ/wr2u7PSpql+nky20 ky2t0Xx610mAMCtGs6stfrNf3OF2RKyyybGuzeV9aYPbXwzF4VIb9h5B37ctFtyBKr8n AS0rJX7h+RAuofh6sbnfYqxpFug/057NKyaRtFgCPtzXCTn7d/EmcW309LOX7m7xlBX8 s+/ZBLz0b6AjdQzfZWZpxFDl3PoUvtd6JdcsZ+bK+UqVDUgXc5lkm7Smw0WDRWKgWKlT kVMLjHs74sBFeovUR+Bfk8PdmzXF7nkyQnzFC/ARhqJIOfblHJW8pB23/Ydt02KmS9zp 1cKw== X-Gm-Message-State: AA6/9RlcLgN1l3t6OfAzJypdOZkwhr4lMmuyrr/8CO/U0KOpKaH95sRyES5MszY9z06Tn4W6 X-Received: by 10.66.165.172 with SMTP id yz12mr4363274pab.208.1475582225256; Tue, 04 Oct 2016 04:57:05 -0700 (PDT) Received: from localhost ([122.171.115.29]) by smtp.gmail.com with ESMTPSA id a137sm54727729pfa.72.2016.10.04.04.57.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Oct 2016 04:57:04 -0700 (PDT) From: Viresh Kumar To: Rafael Wysocki , nm@ti.com, sboyd@codeaurora.org, Viresh Kumar Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Vincent Guittot , robh@kernel.org, d-gerlach@ti.com, broonie@kernel.org, Viresh Kumar , devicetree@vger.kernel.org Subject: [PATCH 1/8] PM / OPP: Reword binding supporting multiple regulators per device Date: Tue, 4 Oct 2016 17:26:43 +0530 Message-Id: X-Mailer: git-send-email 2.7.1.410.g6faf27b In-Reply-To: References: In-Reply-To: References: Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On certain platforms (like TI), DVFS for a single device (CPU) requires configuring multiple power supplies. The OPP bindings already contains binding and example to explain this case, but it isn't sufficient. For example, there is no way for the code parsing these bindings to know which voltage values belong to which power supply. Also its not possible to know the order in which the supplies need to be configured while switching OPPs. This patch tries to clarify on those details and does some minor changes as well. Note that the bindings do not specify the order in which the regulators need to be programmed and the order in which the entries are added for the supplies. The user of the bindings (like the kernel) shall know these details already and the DT is responsible to supply only the readings for the regulators. Cc: Mark Brown Cc: devicetree@vger.kernel.org Signed-off-by: Viresh Kumar --- Documentation/devicetree/bindings/opp/opp.txt | 25 +++++++++++++++++-------- 1 file changed, 17 insertions(+), 8 deletions(-) -- 2.7.1.410.g6faf27b -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt index ee91cbdd95ee..af476df510f1 100644 --- a/Documentation/devicetree/bindings/opp/opp.txt +++ b/Documentation/devicetree/bindings/opp/opp.txt @@ -86,8 +86,13 @@ properties. Single entry is for target voltage and three entries are for voltages. - Entries for multiple regulators must be present in the same order as - regulators are specified in device's DT node. + Entries for multiple regulators shall be provided in the same field separated + by angular brackets <>. The OPP binding doesn't provide any provisions to + relate the values to their power supplies or the order in which the supplies + need to be configured. + + Entries for all regulators shall be of the same size, i.e. either all use a + single value or triplets. - opp-microvolt-: Named opp-microvolt property. This is exactly similar to the above opp-microvolt property, but allows multiple voltage ranges to be @@ -104,10 +109,12 @@ properties. Should only be set if opp-microvolt is set for the OPP. - Entries for multiple regulators must be present in the same order as - regulators are specified in device's DT node. If this property isn't required - for few regulators, then this should be marked as zero for them. If it isn't - required for any regulator, then this property need not be present. + Entries for multiple regulators shall be provided in the same field separated + by angular brackets <>. If current values aren't required for a regulator, + then it shall be filled with 0. If current values aren't required for any of + the regulators, then this field is not required. The OPP binding doesn't + provide any provisions to relate the values to their power supplies or the + order in which the supplies need to be configured. - opp-microamp-: Named opp-microamp property. Similar to opp-microvolt- property, but for microamp instead. @@ -386,10 +393,12 @@ Example 4: Handling multiple regulators / { cpus { cpu@0 { - compatible = "arm,cortex-a7"; + compatible = "vendor,cpu-type"; ... - cpu-supply = <&cpu_supply0>, <&cpu_supply1>, <&cpu_supply2>; + vcc0-supply = <&cpu_supply0>; + vcc1-supply = <&cpu_supply1>; + vcc2-supply = <&cpu_supply2>; operating-points-v2 = <&cpu0_opp_table>; }; };