From: Ansuel Smith <ansuelsmth@gmail.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Ansuel Smith <ansuelsmth@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH v3 2/2] dt-bindings: cpufreq: Document Krait CPU Cache scaling
Date: Fri, 21 Aug 2020 16:00:21 +0200 [thread overview]
Message-ID: <20200821140026.19643-3-ansuelsmth@gmail.com> (raw)
In-Reply-To: <20200821140026.19643-1-ansuelsmth@gmail.com>
Document dedicated Krait CPU Cache Scaling driver.
Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
---
.../bindings/cpufreq/krait-cache-scale.yaml | 79 +++++++++++++++++++
1 file changed, 79 insertions(+)
create mode 100644 Documentation/devicetree/bindings/cpufreq/krait-cache-scale.yaml
diff --git a/Documentation/devicetree/bindings/cpufreq/krait-cache-scale.yaml b/Documentation/devicetree/bindings/cpufreq/krait-cache-scale.yaml
new file mode 100644
index 000000000000..f5f1c9b76656
--- /dev/null
+++ b/Documentation/devicetree/bindings/cpufreq/krait-cache-scale.yaml
@@ -0,0 +1,79 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/cpufreq/krait-cache-scale.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Krait Cpu Cache Frequency Scaling dedicated driver
+
+maintainers:
+ - Ansuel Smith <ansuelsmth@gmail.com>
+
+description: |
+ This Scale the Krait CPU Cache Frequency and optionally voltage
+ when the Cpu Frequency is changed (using the cpufreq notifier).
+
+ Cache is scaled with the max frequency across all core and the cache
+ frequency will scale based on the configured threshold in the dts.
+
+ The cache thresholds can be set to 3+ frequency bin, idle, nominal and
+ high.
+
+properties:
+ compatible:
+ const: qcom,krait-cache
+
+ clocks:
+ $ref: "/schemas/types.yaml#/definitions/phandle"
+ description: Phandle to the L2 CPU clock
+
+ clock-names:
+ const: "l2"
+
+ voltage-tolerance:
+ description: Same voltage tollerance of the Krait CPU
+
+ l2-cpufreq:
+ description: |
+ Threshold used by the driver to scale the L2 cache.
+ If the max CPU Frequency is more than the set frequency,
+ the driver will transition to the next frequency bin.
+ Value is in kHz
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+ minItems: 3
+ items:
+ - description: idle
+ - description: nominal
+ - description: high
+
+ l2-supply:
+ $ref: "/schemas/types.yaml#/definitions/phandle"
+ description: Phandle to the L2 regulator supply.
+
+ opp-table: true
+
+required:
+ - compatible
+ - clocks
+ - clock-names
+ - voltage-tolerance
+ - l2-cpufreq
+ - l2-supply
+
+examples:
+ - |
+ qcom-krait-cache {
+ compatible = "qcom,krait-cache";
+ clocks = <&kraitcc 4>;
+ clock-names = "l2";
+ voltage-tolerance = <5>;
+ l2-cpufreq = <384000 600000 1200000>;
+ l2-supply = <&smb208_s1a>;
+
+ operating-points = <
+ /* kHz uV */
+ 384000 1100000
+ 1000000 1100000
+ 1200000 1150000
+ >;
+ };
--
2.27.0
next prev parent reply other threads:[~2020-08-21 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 14:00 [RFC PATCH v3 0/2] Add Krait Cache Scaling support Ansuel Smith
2020-08-21 14:00 ` [RFC PATCH v3 1/2] cpufreq: qcom: " Ansuel Smith
2020-08-21 14:00 ` Ansuel Smith [this message]
2020-08-24 17:28 ` [RFC PATCH v3 2/2] dt-bindings: cpufreq: Document Krait CPU Cache scaling Rob Herring
2020-08-24 10:40 ` [RFC PATCH v3 0/2] Add Krait Cache Scaling support Viresh Kumar
2020-08-31 5:45 ` Sibi Sankar
2020-08-31 7:41 ` R: " ansuelsmth
2020-09-03 6:53 ` Viresh Kumar
2020-09-03 7:13 ` Sibi Sankar
2020-09-03 11:00 ` R: " ansuelsmth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200821140026.19643-3-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).