From patchwork Thu Nov 5 01:41:54 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Viresh Kumar X-Patchwork-Id: 56013 Delivered-To: patch@linaro.org Received: by 10.112.61.134 with SMTP id p6csp126868lbr; Wed, 4 Nov 2015 17:42:36 -0800 (PST) X-Received: by 10.66.141.73 with SMTP id rm9mr6035603pab.12.1446687756217; Wed, 04 Nov 2015 17:42:36 -0800 (PST) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id ks7si4064983pab.109.2015.11.04.17.42.35; Wed, 04 Nov 2015 17:42:36 -0800 (PST) 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 S1031649AbbKEBma (ORCPT + 28 others); Wed, 4 Nov 2015 20:42:30 -0500 Received: from mail-pa0-f46.google.com ([209.85.220.46]:34219 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031616AbbKEBmX (ORCPT ); Wed, 4 Nov 2015 20:42:23 -0500 Received: by padhx2 with SMTP id hx2so62050513pad.1 for ; Wed, 04 Nov 2015 17:42:23 -0800 (PST) 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=SZAotNbnhChjUyzw5nRiM7KCQVZzducMrXUBQqnfuMo=; b=P3RxMLjOIHhCaGT2d7tzmw4e0KOIg+SM1MwXpuoXiiMJpSzGbHzvZnEY71YC9n0GLx DJgpzRhvPJN0TfevAMUGjizJHdeAajvH05l/DNQojpWG/WFt7da9g0qUURhi6sG0+FWx yH5zqlUwCTFh+d3Y9Bi5rfc9FJo+kYlak/B5PlDyDuWiKtOr5q78tP8ZQzi3OIcNVYDv S8iqjV8Cj7xH2Ze78SsMve//W8irSYl8/Brx3MFiwEVCyz1RozOTdjjdJXQaVBEKPn2x x6ZBDZWTKqhShDzGuePsGutTA0a/hEGIICyHUIwpUXi4/XY2rU3fe5thapRVyI1MUgEs +xsg== 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=SZAotNbnhChjUyzw5nRiM7KCQVZzducMrXUBQqnfuMo=; b=e+7NaF13vRk0G00IoOIkzAngwBDysBuvhLBXiiltXMZg7PEC+SiAUBfN06rdrTkdpl FLau+Mf1qbcpN4ecshcdbWCNuGLdriWxA0IG8+GCoTNj3rod1fqKFtl/sjC1lqe/xlUx Xw/o3VvzmSx1CJ57sHTlw2POtC7hyT853BlP5TrOzYVYCji4Axz0DMw7woBo6sveBAPh 1y2vWsB68gtWLqOEZYUQAuRR6fg1i1Ln3Ac6PYEovBC86pWOL32ccAE1U9fIF2zIFk93 srFYyOg8CgopBzlILgr25eMXbQH2uj06X+Q++O1+ELaCVi7QFOsmVl85eGuz19EVFLiq 4Q0w== X-Gm-Message-State: ALoCoQmpWts8dfyhDma8q288obyvxAOfbzVf1o8at0mDzim1QY7ngDMrnlNOZA2LP2I5od9+AFoH X-Received: by 10.69.8.226 with SMTP id dn2mr6186893pbd.138.1446687742932; Wed, 04 Nov 2015 17:42:22 -0800 (PST) Received: from localhost ([122.172.111.169]) by smtp.gmail.com with ESMTPSA id qy3sm4434785pbc.21.2015.11.04.17.42.21 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 04 Nov 2015 17:42:22 -0800 (PST) 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, b.zolnierkie@samsung.com, m.szyprowski@samsung.com, Viresh Kumar , linux-kernel@vger.kernel.org (open list), "Rafael J. Wysocki" Subject: [PATCH V2 3/5] PM / OPP: Remove 'operating-points-names' binding Date: Thu, 5 Nov 2015 07:11:54 +0530 Message-Id: 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. Reviewed-by: Stephen Boyd 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 61c6f25cf8e2..30c4bb3718bc 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 @@ -454,54 +443,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) / { @@ -546,7 +488,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)