From patchwork Wed Nov 30 05:14:05 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Viresh Kumar X-Patchwork-Id: 84946 Delivered-To: patch@linaro.org Received: by 10.140.20.101 with SMTP id 92csp86889qgi; Tue, 29 Nov 2016 21:14:37 -0800 (PST) X-Received: by 10.84.192.1 with SMTP id b1mr69501200pld.113.1480482877104; Tue, 29 Nov 2016 21:14:37 -0800 (PST) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z3si62651981pge.291.2016.11.29.21.14.36; Tue, 29 Nov 2016 21:14:37 -0800 (PST) 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 S1751529AbcK3FOf (ORCPT + 13 others); Wed, 30 Nov 2016 00:14:35 -0500 Received: from mail-pg0-f43.google.com ([74.125.83.43]:34555 "EHLO mail-pg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751404AbcK3FOf (ORCPT ); Wed, 30 Nov 2016 00:14:35 -0500 Received: by mail-pg0-f43.google.com with SMTP id x23so77790096pgx.1 for ; Tue, 29 Nov 2016 21:14:34 -0800 (PST) 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=WPDIA+zdQT5iqTG6D37udj7somTJ2RMVlIVJ/Q04k4U=; b=adtglLd/3hdKWKU4wWm0tE4cEMNP24h5c1MxpAH4tRqvRC3WBzYOWyiITyrIQ1bsyq 1bjXJoQZD1TjTsky/Qqqgc+kr+ub+lF6YAb/PxvsIetEFlRjbsTVc3K2UAWan3mQiDbm ZkxiFJOKEhP/CsoNqGJvdC3OFeEBBB6qAkZr4= 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=WPDIA+zdQT5iqTG6D37udj7somTJ2RMVlIVJ/Q04k4U=; b=ZFtMHo4Nz5fE+tLsEUvizzgVLqqfHm/EGkioxWloj9SqXmwOV5h6KMhwWE6mkk5+A1 KDB7SBstfox1DqNn0cGZelRvd4ZRkiS8Izu08tVhQ/PCHFMPlnwej37LFt5z3a26EThz W9CnuSvItqzoOooy3sHbcIr9OXASigyBk4JkSErT0SGA/5dSLa9EWEfo4dEk5sHWAmds KuCS2BUC1XKyhmqrVnzkM1BJVNh4esGG0Hr6wlgNE2Jp+FlKv0GsfBqEHuf/XjzrMtYJ y7nYu1rg84nzJ5p1UjYMoa+y8jbXzidi8FkwjGioHjDevVWZNCLbS0BFKLGQ85npK5yu n4mg== X-Gm-Message-State: AKaTC01f9IS/MBX6zZjBWCVCwRLWzVpYPAwsAqTJ4yokATJV5YGqB1S3LgE+Vy99zDOKsBQ6 X-Received: by 10.84.137.1 with SMTP id 1mr68227139plm.8.1480482874220; Tue, 29 Nov 2016 21:14:34 -0800 (PST) Received: from localhost ([122.172.143.30]) by smtp.gmail.com with ESMTPSA id z9sm81093736pge.44.2016.11.29.21.14.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Nov 2016 21:14:33 -0800 (PST) From: Viresh Kumar To: Rafael Wysocki , Viresh Kumar , Nishanth Menon , Stephen Boyd Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, Vincent Guittot , robh@kernel.org, d-gerlach@ti.com, broonie@kernel.org, devicetree@vger.kernel.org, Viresh Kumar Subject: [PATCH V6 02/10] PM / OPP: Reword binding supporting multiple regulators per device Date: Wed, 30 Nov 2016 10:44:05 +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. - There is no way for the code parsing these bindings to know which voltage values belong to which power supply. - It is not possible to know the order in which the supplies need to be configured while switching OPPs. This patch clarifies on those details by mentioning that such information is left for the implementation specific bindings to explain. They may want to hardcode such details or implement their own properties to get such information. All implementations using multiple regulators for their devices must provide a binding document explaining their implementation. Signed-off-by: Viresh Kumar Acked-by: Rob Herring Reviewed-by: Stephen Boyd --- Documentation/devicetree/bindings/opp/opp.txt | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 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 f0239f68d186..9f5ca4457b5f 100644 --- a/Documentation/devicetree/bindings/opp/opp.txt +++ b/Documentation/devicetree/bindings/opp/opp.txt @@ -86,8 +86,14 @@ 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 and that is left for the implementation specific + binding. + + 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 +110,13 @@ 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 and that is left for the + implementation specific binding. - opp-microamp-: Named opp-microamp property. Similar to opp-microvolt- property, but for microamp instead.