From: Jun Nie <jun.nie@linaro.org>
To: myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
cw00.choi@samsung.com
Cc: bryan.odonoghue@linaro.org, linux-pm@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Jun Nie <jun.nie@linaro.org>
Subject: [PATCH 1/2] dt-bindings: interconnect: Add Qualcomm CCI dt-bindings
Date: Wed, 1 Feb 2023 16:02:26 +0800 [thread overview]
Message-ID: <20230201080227.473547-1-jun.nie@linaro.org> (raw)
Add devicetree binding of Qualcomm CCI on MSM8939.
Signed-off-by: Jun Nie <jun.nie@linaro.org>
---
.../bindings/interconnect/qcom,cci.yaml | 81 +++++++++++++++++++
1 file changed, 81 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,cci.yaml
diff --git a/Documentation/devicetree/bindings/interconnect/qcom,cci.yaml b/Documentation/devicetree/bindings/interconnect/qcom,cci.yaml
new file mode 100644
index 000000000000..100c440ba220
--- /dev/null
+++ b/Documentation/devicetree/bindings/interconnect/qcom,cci.yaml
@@ -0,0 +1,81 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/interconnect/mediatek,cci.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Qualcomm Cache Coherent Interconnect (CCI) frequency and voltage scaling
+
+maintainers:
+ - Jun Nie <jun.nie@linaro.org>
+
+description: |
+ Qualcomm Cache Coherent Interconnect (CCI) is a hardware engine used by
+ MSM8939. The driver is to scale its frequency and adjust the voltage in
+ hardware accordingly. The voltage provider is modeled as power domain on
+ MSM8939, so power domain dts node is required.
+
+properties:
+ compatible:
+ enum:
+ - qcom,msm8939-cci
+
+ clocks:
+ maxItems: 1
+
+ operating-points-v2: true
+ opp-table:
+ type: object
+
+required:
+ - compatible
+ - clocks
+ - operating-points-v2
+ - nvmem-cells
+ - power-domains
+
+additionalProperties: false
+
+examples:
+ - |
+ cci: cci {
+ compatible = "qcom,msm8939-cci";
+ clocks = <&apcs2>;
+ operating-points-v2 = <&cci_opp_table>;
+ power-domains = <&cpr>;
+ nvmem-cells = <&cpr_efuse_speedbin_pvs>;
+ };
+
+ cci_opp_table: cci-opp-table {
+ compatible = "operating-points-v2";
+
+ cci_opp1: opp-200000000 {
+ opp-hz = /bits/ 64 <200000000>;
+ opp-supported-hw = <0x3f>;
+ required-opps = <&cpr_opp3>;
+ };
+
+ cci_opp2: opp-297600000 {
+ opp-hz = /bits/ 64 <297600000>;
+ opp-supported-hw = <0x3f>;
+ required-opps = <&cpr_opp12>;
+ };
+
+ cci_opp3: opp-400000000 {
+ opp-hz = /bits/ 64 <400000000>;
+ opp-supported-hw = <0x1>;
+ required-opps = <&cpr_opp14>;
+ };
+
+ cci_opp4: opp-400000000 {
+ opp-hz = /bits/ 64 <400000000>;
+ opp-supported-hw = <0x3e>;
+ required-opps = <&cpr_opp15>;
+ };
+
+ cci_opp5: opp-595200000 {
+ opp-hz = /bits/ 64 <595200000>;
+ opp-supported-hw = <0x3f>;
+ required-opps = <&cpr_opp17>;
+ };
+ };
--
2.34.1
next reply other threads:[~2023-02-01 8:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 8:02 Jun Nie [this message]
2023-02-01 8:02 ` [PATCH 2/2] PM / devfreq: qcom: Introduce CCI devfreq driver Jun Nie
2023-02-01 8:48 ` Krzysztof Kozlowski
2023-02-01 15:15 ` Jun Nie
2023-02-01 10:27 ` Bryan O'Donoghue
2023-02-01 11:02 ` Chanwoo Choi
2023-02-01 15:17 ` Jun Nie
2023-02-01 17:18 ` Dmitry Baryshkov
2023-02-01 11:32 ` Dmitry Baryshkov
2023-02-01 11:46 ` Bryan O'Donoghue
2023-02-01 13:41 ` Dmitry Baryshkov
2023-02-01 14:45 ` Bryan O'Donoghue
2023-02-01 14:58 ` Dmitry Baryshkov
2023-02-01 15:17 ` Bryan O'Donoghue
2023-02-01 17:12 ` Dmitry Baryshkov
2023-02-01 17:16 ` Bryan O'Donoghue
2023-02-01 17:19 ` Dmitry Baryshkov
2023-02-02 12:55 ` Jun Nie
2023-02-01 15:23 ` Jun Nie
2023-02-01 8:43 ` [PATCH 1/2] dt-bindings: interconnect: Add Qualcomm CCI dt-bindings Krzysztof Kozlowski
2023-02-02 9:29 ` Jun Nie
2023-02-02 9:42 ` Krzysztof Kozlowski
2023-02-03 3:45 ` Jun Nie
2023-02-03 7:06 ` Krzysztof Kozlowski
2023-02-01 10:46 ` Chanwoo Choi
2023-02-01 14:23 ` Rob Herring
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=20230201080227.473547-1-jun.nie@linaro.org \
--to=jun.nie@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
/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).