Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp3283291imm; Fri, 25 May 2018 03:03:28 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrLkBHa9ldUI3T5dS35Y2dyL6FO6tyuO+XihQg8h6BZ483044XyFu4nEF42HTlB9iqyXAGB X-Received: by 2002:a17:902:1007:: with SMTP id b7-v6mr1889608pla.88.1527242607984; Fri, 25 May 2018 03:03:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527242607; cv=none; d=google.com; s=arc-20160816; b=gFBgQe68GYdzeDDSS84sD1eZqTEOZMWnAWQyOphisL+4iZrtG3WG/7Prr4Dl0Nrv7S Wv8Y7kF6zkIjQAz3z8+8K5kHKNPPntGAX8Q1nWZA+umCRKoFs0DrjE7q+RfKlTCGBXGs F+l8UNmpJfqBEZSp8WaNQsEhiPZUY58GRnj9SZK9M3TJfeFzcXRxzlbvd2DrYiPTcqOg vxVSAa7hKgPmaxN1XMbccadE9Mr/A3912PmC0r1tew147L12yN118kBZsyogp1mOo2dd zn8nEcpZQge1oMLjv25G19CXaAwWVPQaUpxKnXEE+SVpYehisQwVv0e/wn0Z+u7EWcao mwVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dmarc-filter:dkim-signature:dkim-signature :arc-authentication-results; bh=Hyjgn2AI57HvMKq0l4X8rjkSpL0uNhxjRV8dDvpczDU=; b=mEd6ceAEbf9sNclqfZh/ibAzXjhadCe64BcPFEbXsWqpzdP0HZZf6bnPZuu5pVJ+A3 ru0c7rdHMfyq+uy+4M29VoTNiK95tyjEkVu1aLMZ4QLqFmRGi0cz0BnTr2WvQRJGADz0 PYFsHfQYO+RUGSThXFP2q8l3/gCyZcYryekeFG4pZQUI2BWJvEiXB9keVr1oGtOFruFO IS6h8ueZme3JpV6cPVVhIbuW2HUjZ1Wve3vkSHNVQcK+03E4zlu6zOyETeraVV5JRciJ Yp8X55KipoMUYZJSGspUgO9jBokxDjYRFB9GE7dPOtx4b0xsV90dCg+SvoX/vdEfcsMw PFVg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=H0eAUqJ/; dkim=pass header.i=@codeaurora.org header.s=default header.b=baIOfFR9; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r6-v6si8475381pgp.482.2018.05.25.03.03.13; Fri, 25 May 2018 03:03:27 -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; dkim=pass header.i=@codeaurora.org header.s=default header.b=H0eAUqJ/; dkim=pass header.i=@codeaurora.org header.s=default header.b=baIOfFR9; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965805AbeEYKBs (ORCPT + 99 others); Fri, 25 May 2018 06:01:48 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:45702 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965657AbeEYKBk (ORCPT ); Fri, 25 May 2018 06:01:40 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 190E060290; Fri, 25 May 2018 10:01:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1527242500; bh=R7UbEQrKv1U1FIdVslcjaAYCIBhOUFddZQiFlmKmqwI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=H0eAUqJ/rti72XmouAW7PjFlkDfNGZLxx4DNelpcrzd1b0c16YIvnOGp1AVBOEXOE ZEP6Sibn36/pYSKOA3oMIYGVY2CjSH6N5Qjs/AAH+PfCy8N5w9pXd91fUzPv8/8B7U HkFgDYvPwgPjul2rOQkIgLIuDI/yGX28FjYJhosQ= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from blr-ubuntu-173.qualcomm.com (blr-bdr-fw-01_globalnat_allzones-outside.qualcomm.com [103.229.18.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: rnayak@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 4ADFA60FEA; Fri, 25 May 2018 10:01:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1527242499; bh=R7UbEQrKv1U1FIdVslcjaAYCIBhOUFddZQiFlmKmqwI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=baIOfFR9gxygD/OXBntA+9XwY6sTQC57KqkNb6JVeBTNG8aBdgLUSm+MysX+/yMYY qRW3a3/ntVFML1GIY91z8lpGSjzBnWsWUZmaIkKZ4bHh31c4P4P/eXiIymd6qG+PM1 Fib+Z0VP6rsX3/YxOxgTqGg32m5rQLtCo/pZD0UA= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 4ADFA60FEA Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=rnayak@codeaurora.org From: Rajendra Nayak To: viresh.kumar@linaro.org, sboyd@kernel.org, andy.gross@linaro.org, ulf.hansson@linaro.org Cc: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, collinsd@codeaurora.org, Rajendra Nayak Subject: [PATCH v2 2/6] dt-bindings: opp: Introduce qcom-opp bindings Date: Fri, 25 May 2018 15:31:17 +0530 Message-Id: <20180525100121.28214-3-rnayak@codeaurora.org> X-Mailer: git-send-email 2.17.0 In-Reply-To: <20180525100121.28214-1-rnayak@codeaurora.org> References: <20180525100121.28214-1-rnayak@codeaurora.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Qualcomm platforms, an OPP node needs to describe an additional level/corner value that is then communicated to a remote microprocessor by the CPU, which then takes some actions (like adjusting voltage values across various rails) based on the value passed. Describe these bindings in the qcom-opp bindings document. Signed-off-by: Rajendra Nayak Acked-by: Viresh Kumar Reviewed-by: Rob Herring --- .../devicetree/bindings/opp/qcom-opp.txt | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 Documentation/devicetree/bindings/opp/qcom-opp.txt diff --git a/Documentation/devicetree/bindings/opp/qcom-opp.txt b/Documentation/devicetree/bindings/opp/qcom-opp.txt new file mode 100644 index 000000000000..db4d970c7ec7 --- /dev/null +++ b/Documentation/devicetree/bindings/opp/qcom-opp.txt @@ -0,0 +1,25 @@ +Qualcomm OPP bindings to descibe OPP nodes with corner/level values + +OPP tables for devices on Qualcomm platforms require an additional +platform specific corner/level value to be specified. +This value is passed on to the RPM (Resource Power Manager) by +the CPU, which then takes the necessary actions to set a voltage +rail to an appropriate voltage based on the value passed. + +The bindings are based on top of the operating-points-v2 bindings +described in Documentation/devicetree/bindings/opp/opp.txt +Additional properties are described below. + +* OPP Table Node + +Required properties: +- compatible: Allow OPPs to express their compatibility. It should be: + "operating-points-v2-qcom-level" + +* OPP Node + +Required properties: +- qcom,level: On Qualcomm platforms an OPP node can describe a positive value +representing a corner/level that's communicated with a remote microprocessor +(usually called the RPM) which then translates it into a certain voltage on +a voltage rail. -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation