From patchwork Thu Apr 30 12:08:00 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Viresh Kumar X-Patchwork-Id: 6302481 Return-Path: X-Original-To: patchwork-linux-arm@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.136]) by patchwork2.web.kernel.org (Postfix) with ESMTP id 61606BEEE1 for ; Thu, 30 Apr 2015 12:12:22 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 87FC5201FA for ; Thu, 30 Apr 2015 12:12:21 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.9]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A42892018E for ; Thu, 30 Apr 2015 12:12:19 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1YnnHD-0005yw-Su; Thu, 30 Apr 2015 12:09:11 +0000 Received: from mail-pd0-f176.google.com ([209.85.192.176]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1YnnGh-0005g5-1j for linux-arm-kernel@lists.infradead.org; Thu, 30 Apr 2015 12:08:39 +0000 Received: by pdbqa5 with SMTP id qa5so58856397pdb.1 for ; Thu, 30 Apr 2015 05:08:17 -0700 (PDT) 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=9s2YHT+7Y/AnjumQAwf5ISdlopvDcVL1URNrMaucNB8=; b=kEn+naeRhlwWAWWHmCiqy+MeLgrRLF0A+TyKzaRhusYTxSizytqlkjHxderQaK5kDq c/s2QrrTK/e3EQ9dL+ojJTZYav9AcD/RHi4qifmJ3Hu4HkZkuHQ8ZFh2fqmdvpeeLtwm NsietIs31jM0HnBMnAYeIQl+pMZs1yVpTFLATjR+GGjiXqmOyfaX0+8nM2eJUOBqfqxB 4G5BfulK9WCdp1t4FU/6QPWVE3TOtFqKEE0lP6OXfLeL3fAP7GGlazoKK26XPmESDRcz wDvRBM+VBPKbF9DTtL6Rk0U4JMP0Sev9UcdjmaA03pJuh90xlbKnOAmOJIUe4RFhhwbW hyCw== X-Gm-Message-State: ALoCoQkf8gIXqZgZOep4P1hsEu6tPwV5T0jFMnycO8LbH0vsrzIWZeovzwpTIFaqDTS+NX01+Ju7 X-Received: by 10.70.25.37 with SMTP id z5mr7791250pdf.36.1430395697492; Thu, 30 Apr 2015 05:08:17 -0700 (PDT) Received: from localhost ([122.178.211.250]) by mx.google.com with ESMTPSA id fm3sm2062320pdb.28.2015.04.30.05.08.16 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 30 Apr 2015 05:08:16 -0700 (PDT) From: Viresh Kumar To: Rafael Wysocki , rob.herring@linaro.org, arnd.bergmann@linaro.org, nm@ti.com, broonie@kernel.org, mike.turquette@linaro.org, sboyd@codeaurora.org Subject: [PATCH V4 2/3] OPP: Allow multiple OPP tables to be passed via DT Date: Thu, 30 Apr 2015 17:38:00 +0530 Message-Id: X-Mailer: git-send-email 2.3.0.rc0.44.ga94655d In-Reply-To: References: In-Reply-To: References: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20150430_050839_164266_1965562F X-CRM114-Status: GOOD ( 10.28 ) X-Spam-Score: -0.3 (/) Cc: thomas.petazzoni@free-electrons.com, devicetree@vger.kernel.org, kesavan.abhilash@gmail.com, linaro-kernel@lists.linaro.org, ta.omasab@gmail.com, linux-pm@vger.kernel.org, viswanath.puttagunta@linaro.org, Viresh Kumar , santosh.shilimkar@oracle.com, olof@lixom.net, khilman@linaro.org, Sudeep.Holla@arm.com, grant.likely@linaro.org, linux-arm-kernel@lists.infradead.org, l.stach@pengutronix.de X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@lists.infradead.org X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_MED, RCVD_IN_SORBS_WEB, T_RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP On some platforms (Like Qualcomm's SoCs), it is not decided until runtime on what OPPs to use. The OPP tables can be fixed at compile time, but which table to use is found out only after reading some efuses (sort of an eeprom) and knowing characteristics of the SoC. To support such platform we need to pass multiple OPP tables per device and hardware should be able to choose one and only one table out of those. Update OPP-v2 bindings to support that. Signed-off-by: Viresh Kumar Acked-by: Nishanth Menon Reviewed-by: Stephen Boyd --- Documentation/devicetree/bindings/power/opp.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/devicetree/bindings/power/opp.txt b/Documentation/devicetree/bindings/power/opp.txt index 3b67a5c8d965..07959903ec32 100644 --- a/Documentation/devicetree/bindings/power/opp.txt +++ b/Documentation/devicetree/bindings/power/opp.txt @@ -14,6 +14,9 @@ Devices supporting OPPs must set their "operating-points-v2" property with phandle to a OPP descriptor 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. + * OPP Descriptor Node @@ -28,6 +31,8 @@ This describes the OPPs belonging to a device. This node can have following reference an OPP. Optional properties: +- opp-name: Name of the OPP table, to uniquely identify it if more than one OPP + table is supplied in "operating-points-v2" property of device. - shared-opp: Indicates that device nodes using this OPP descriptor's phandle switch their DVFS state together, i.e. they share clock/voltage/current lines. Missing property means devices have independent clock/voltage/current lines,