linux-kernel - [PATCH v9 01/10] dt-bindings: opp: Introduce opp-level bindings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon,  7 Jan 2019 15:39:50 +0530
From:   Rajendra Nayak <rnayak@...eaurora.org>
To:     andy.gross@...aro.org, robh@...nel.org, viresh.kumar@...aro.org,
        sboyd@...nel.org, ulf.hansson@...aro.org, collinsd@...eaurora.org,
        mka@...omium.org
Cc:     devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        linux-kernel@...r.kernel.org, henryc.chen@...iatek.com,
        Rajendra Nayak <rnayak@...eaurora.org>
Subject: [PATCH v9 01/10] dt-bindings: opp: Introduce opp-level bindings

On some SoCs (especially from Qualcomm and MediaTek) 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 opp-level bindings document.

Signed-off-by: Rajendra Nayak <rnayak@...eaurora.org>
---
 .../devicetree/bindings/opp/opp-level.txt     | 29 +++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/opp/opp-level.txt

diff --git a/Documentation/devicetree/bindings/opp/opp-level.txt b/Documentation/devicetree/bindings/opp/opp-level.txt
new file mode 100644
index 000000000000..f9134ed08164
--- /dev/null
+++ b/Documentation/devicetree/bindings/opp/opp-level.txt
@@ -0,0 +1,29 @@
+OPP level bindings to descibe OPP nodes with corner/level values
+
+OPP tables for devices on some SoCs, especially from Qualcomm and
+MediaTek require an additional platform specific corner/level
+value to be specified.
+This value is passed on to a 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,
+with the exception that all of the properties are now optional,
+including the opp-hz property.
+
+Additional properties are described below.
+
+* OPP Table Node
+
+Required properties:
+- compatible: Allow OPPs to express their compatibility. It should be:
+  "operating-points-v2-level"
+
+* OPP Node
+
+Required properties:
+- opp-level: On some SoC platforms an OPP node can describe a positive value
+representing a corner/level that's communicated with a remote microprocessor
+(usually called the power manager) 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