From patchwork Fri Oct 30 01:25:07 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Viresh Kumar X-Patchwork-Id: 55810 Delivered-To: patch@linaro.org Received: by 10.112.61.134 with SMTP id p6csp883391lbr; Thu, 29 Oct 2015 18:26:00 -0700 (PDT) X-Received: by 10.66.123.72 with SMTP id ly8mr5461880pab.92.1446168360169; Thu, 29 Oct 2015 18:26:00 -0700 (PDT) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id fj6si6700032pad.24.2015.10.29.18.25.59; Thu, 29 Oct 2015 18:26:00 -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; dkim=neutral (body hash did not verify) header.i=@linaro_org.20150623.gappssmtp.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758170AbbJ3BZr (ORCPT + 28 others); Thu, 29 Oct 2015 21:25:47 -0400 Received: from mail-pa0-f51.google.com ([209.85.220.51]:34855 "EHLO mail-pa0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758147AbbJ3BZk (ORCPT ); Thu, 29 Oct 2015 21:25:40 -0400 Received: by pasz6 with SMTP id z6so56814300pas.2 for ; Thu, 29 Oct 2015 18:25:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro_org.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :in-reply-to:references; bh=5e/yBI66zv8+7HdpS8YBJfXIczloUQGCJ1gImrM8UQ8=; b=oUSDQg38qgQfLZs71JeDbXt409cVF6IP+2dUGwLuYUxVls2zXNDXnHaBulAhWKd8Bx IEzzfEhJT7UJC4j9XqR+dCP91K2MUZd2IkkhpTe8lrlvdU/YNluFcGmXWvL7mozopI8A sxcSdSgOLUWUj4tlfe4YGJVUl/qvfkFBD31etqxGr1V9d/IRr+J+Wk0znksEQ45wORoh UC5ct3h9MTli2vFcNegBWT9SfGkha5y30Mrz1sSVkPqOT7LHXnZSJ2TcRaw5fsd3ZF5j ZUt40xCIScnDZdt3Rryv92j75kyjyAmM6Dg38b5jaM+hVnffw3BIAdHTOHLvCYa7xXHV aKlA== 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=5e/yBI66zv8+7HdpS8YBJfXIczloUQGCJ1gImrM8UQ8=; b=VKEmOkeaXr/QAaKBAWIpmUGUzgwaoJttDT+vFdfbcm/zfZB3ZSwhKFyjxxTIbqb+Jy 4klnWVvQQiO/40pnnT39GjKDo7xCDeYdggkFCgbOZNieR3nXjzbnLXZVph+aRw6OqiD6 gOHbHOSJK2IyN+9a1/dFPFGGarTVpUhXg5oM7nfkgiTo9lyUbtiBqzApAJGnpPWDl+MM qzbPqBPIN0BGbhKdxC4bc+cbsUptj3Mi9Ch1gHo/2T9V5TbOybyvISQIzedbAMRGRDoT oXygg1/W0inOXRnTUkp4TTpsd5B5z72f59hyJSlJNuYfYF6oqP8RAyoiP6cI/DMWagf1 Au6A== X-Gm-Message-State: ALoCoQnOmxSQDQW3WuFLDa3twGbKfKk7O2hzk5oMOs0Q9DQH3Ns2VlW62nj7tasHfzM1MsdPbVOJ X-Received: by 10.68.221.133 with SMTP id qe5mr5488731pbc.93.1446168339695; Thu, 29 Oct 2015 18:25:39 -0700 (PDT) Received: from localhost ([122.172.111.169]) by smtp.gmail.com with ESMTPSA id j16sm4648730pbq.23.2015.10.29.18.25.38 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 29 Oct 2015 18:25:39 -0700 (PDT) From: Viresh Kumar To: Rafael Wysocki , robh+dt@kernel.org, sboyd@codeaurora.org, lee.jones@linaro.org Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, mark.rutland@arm.com, pawel.moll@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, nm@ti.com, devicetree@vger.kernel.org, Viresh Kumar , linux-kernel@vger.kernel.org (open list), "Rafael J. Wysocki" Subject: [PATCH 3/3] PM / OPP: Remove 'operating-points-names' binding Date: Fri, 30 Oct 2015 06:55:07 +0530 Message-Id: <0290b40c1cb5062335b74ad7e845a1f1d3111f13.1446167359.git.viresh.kumar@linaro.org> X-Mailer: git-send-email 2.6.2.198.g614a2ac In-Reply-To: References: In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org These aren't used until now by any DT files and wouldn't be used now as we have a better scheme in place now, i.e. opp-property- properties. Remove the (useless) binding without breaking ABI. Signed-off-by: Viresh Kumar --- Documentation/devicetree/bindings/opp/opp.txt | 62 +-------------------------- 1 file changed, 2 insertions(+), 60 deletions(-) -- 2.6.2.198.g614a2ac -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt index 6e0dd8db3b86..9d2e08f488b5 100644 --- a/Documentation/devicetree/bindings/opp/opp.txt +++ b/Documentation/devicetree/bindings/opp/opp.txt @@ -45,21 +45,10 @@ Devices supporting OPPs must set their "operating-points-v2" property with phandle to a OPP table in their DT node. The OPP core will use this phandle to find the operating points for the device. -Devices may want to choose OPP tables at runtime and so can provide a list of -phandles here. But only *one* of them should be chosen at runtime. This must be -accompanied by a corresponding "operating-points-names" property, to uniquely -identify the OPP tables. - If required, this can be extended for SoC vendor specfic bindings. Such bindings should be documented as Documentation/devicetree/bindings/power/-opp.txt and should have a compatible description like: "operating-points-v2-". -Optional properties: -- operating-points-names: Names of OPP tables (required if multiple OPP - tables are present), to uniquely identify them. The same list must be present - for all the CPUs which are sharing clock/voltage rails and hence the OPP - tables. - * OPP Table Node This describes the OPPs belonging to a device. This node can have following @@ -446,54 +435,7 @@ Example 4: Handling multiple regulators }; }; -Example 5: Multiple OPP tables - -/ { - cpus { - cpu@0 { - compatible = "arm,cortex-a7"; - ... - - cpu-supply = <&cpu_supply> - operating-points-v2 = <&cpu0_opp_table_slow>, <&cpu0_opp_table_fast>; - operating-points-names = "slow", "fast"; - }; - }; - - cpu0_opp_table_slow: opp_table_slow { - compatible = "operating-points-v2"; - status = "okay"; - opp-shared; - - opp00 { - opp-hz = /bits/ 64 <600000000>; - ... - }; - - opp01 { - opp-hz = /bits/ 64 <800000000>; - ... - }; - }; - - cpu0_opp_table_fast: opp_table_fast { - compatible = "operating-points-v2"; - status = "okay"; - opp-shared; - - opp10 { - opp-hz = /bits/ 64 <1000000000>; - ... - }; - - opp11 { - opp-hz = /bits/ 64 <1100000000>; - ... - }; - }; -}; - -Example 6: opp-supported-hw +Example 5: opp-supported-hw (example: three level hierarchy of versions: cuts, substrate and process) / { @@ -538,7 +480,7 @@ Example 6: opp-supported-hw }; }; -Example 7: opp-microvolt-, opp-microamp-, turbo-mode-, +Example 6: opp-microvolt-, opp-microamp-, turbo-mode-, opp-suspend-: (example: device with two possible microvolt ranges: slow and fast)