Update the RPMHPD references with new bindings defined in rpmhpd.h
for Qualcomm SoCs SM8[2345]50.
Signed-off-by: Rohit Agarwal <[email protected]>
---
Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml | 4 ++--
Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml | 4 ++--
Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml | 4 ++--
Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml | 4 ++--
Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml | 4 ++--
Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml | 4 ++--
Documentation/devicetree/bindings/clock/qcom,videocc.yaml | 4 ++--
.../devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml | 4 ++--
.../devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml | 8 ++++----
.../devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml | 4 ++--
.../devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml | 6 +++---
.../devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml | 4 ++--
.../devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml | 8 ++++----
.../devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml | 4 ++--
.../devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml | 8 ++++----
Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml | 4 ++--
Documentation/devicetree/bindings/mmc/sdhci-msm.yaml | 4 ++--
Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml | 6 +++---
18 files changed, 44 insertions(+), 44 deletions(-)
diff --git a/Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml b/Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml
index d6774db..59cc88a 100644
--- a/Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml
+++ b/Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml
@@ -82,7 +82,7 @@ additionalProperties: false
examples:
- |
#include <dt-bindings/clock/qcom,rpmh.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
clock-controller@af00000 {
compatible = "qcom,sm8250-dispcc";
reg = <0x0af00000 0x10000>;
@@ -103,7 +103,7 @@ examples:
#clock-cells = <1>;
#reset-cells = <1>;
#power-domain-cells = <1>;
- power-domains = <&rpmhpd SM8250_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
required-opps = <&rpmhpd_opp_low_svs>;
};
...
diff --git a/Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml b/Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml
index 23505c8..d723bb1 100644
--- a/Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml
+++ b/Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml
@@ -51,7 +51,7 @@ unevaluatedProperties: false
examples:
- |
#include <dt-bindings/clock/qcom,rpmh.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
clock-controller@abf0000 {
compatible = "qcom,sm8350-videocc";
@@ -59,7 +59,7 @@ examples:
clocks = <&rpmhcc RPMH_CXO_CLK>,
<&rpmhcc RPMH_CXO_CLK_A>,
<&sleep_clk>;
- power-domains = <&rpmhpd SM8350_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
required-opps = <&rpmhpd_opp_low_svs>;
#clock-cells = <1>;
#reset-cells = <1>;
diff --git a/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml b/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml
index 87ae741..8178c35 100644
--- a/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml
+++ b/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml
@@ -64,7 +64,7 @@ examples:
- |
#include <dt-bindings/clock/qcom,gcc-sm8450.h>
#include <dt-bindings/clock/qcom,rpmh.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
clock-controller@ade0000 {
compatible = "qcom,sm8450-camcc";
reg = <0xade0000 0x20000>;
@@ -72,7 +72,7 @@ examples:
<&rpmhcc RPMH_CXO_CLK>,
<&rpmhcc RPMH_CXO_CLK_A>,
<&sleep_clk>;
- power-domains = <&rpmhpd SM8450_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
required-opps = <&rpmhpd_opp_low_svs>;
#clock-cells = <1>;
#reset-cells = <1>;
diff --git a/Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml b/Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml
index 1dd1f69..2f22310 100644
--- a/Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml
+++ b/Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml
@@ -76,7 +76,7 @@ examples:
- |
#include <dt-bindings/clock/qcom,gcc-sm8450.h>
#include <dt-bindings/clock/qcom,rpmh.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
clock-controller@af00000 {
compatible = "qcom,sm8450-dispcc";
reg = <0x0af00000 0x10000>;
@@ -91,7 +91,7 @@ examples:
#clock-cells = <1>;
#reset-cells = <1>;
#power-domain-cells = <1>;
- power-domains = <&rpmhpd SM8450_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
required-opps = <&rpmhpd_opp_low_svs>;
};
...
diff --git a/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml b/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
index f1c6dd5..bad8f01 100644
--- a/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
+++ b/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
@@ -64,13 +64,13 @@ examples:
- |
#include <dt-bindings/clock/qcom,gcc-sm8450.h>
#include <dt-bindings/clock/qcom,rpmh.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
videocc: clock-controller@aaf0000 {
compatible = "qcom,sm8450-videocc";
reg = <0x0aaf0000 0x10000>;
clocks = <&rpmhcc RPMH_CXO_CLK>,
<&gcc GCC_VIDEO_AHB_CLK>;
- power-domains = <&rpmhpd SM8450_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
required-opps = <&rpmhpd_opp_low_svs>;
#clock-cells = <1>;
#reset-cells = <1>;
diff --git a/Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml b/Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml
index ab25f7c..c129f8c 100644
--- a/Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml
+++ b/Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml
@@ -76,7 +76,7 @@ examples:
- |
#include <dt-bindings/clock/qcom,sm8550-gcc.h>
#include <dt-bindings/clock/qcom,rpmh.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
clock-controller@af00000 {
compatible = "qcom,sm8550-dispcc";
reg = <0x0af00000 0x10000>;
@@ -99,7 +99,7 @@ examples:
#clock-cells = <1>;
#reset-cells = <1>;
#power-domain-cells = <1>;
- power-domains = <&rpmhpd SM8550_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
required-opps = <&rpmhpd_opp_low_svs>;
};
...
diff --git a/Documentation/devicetree/bindings/clock/qcom,videocc.yaml b/Documentation/devicetree/bindings/clock/qcom,videocc.yaml
index 2b07146..6de01cf 100644
--- a/Documentation/devicetree/bindings/clock/qcom,videocc.yaml
+++ b/Documentation/devicetree/bindings/clock/qcom,videocc.yaml
@@ -124,7 +124,7 @@ additionalProperties: false
examples:
- |
#include <dt-bindings/clock/qcom,rpmh.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
clock-controller@ab00000 {
compatible = "qcom,sdm845-videocc";
reg = <0x0ab00000 0x10000>;
@@ -133,7 +133,7 @@ examples:
#clock-cells = <1>;
#reset-cells = <1>;
#power-domain-cells = <1>;
- power-domains = <&rpmhpd SM8250_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
required-opps = <&rpmhpd_opp_low_svs>;
};
...
diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml
index 687c8c1..acd2ed3 100644
--- a/Documentation/devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml
+++ b/Documentation/devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml
@@ -54,7 +54,7 @@ examples:
#include <dt-bindings/clock/qcom,gcc-sm8250.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/interconnect/qcom,sm8250.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
display-controller@ae01000 {
compatible = "qcom,sm8250-dpu";
@@ -72,7 +72,7 @@ examples:
assigned-clock-rates = <19200000>;
operating-points-v2 = <&mdp_opp_table>;
- power-domains = <&rpmhpd SM8250_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
interrupt-parent = <&mdss>;
interrupts = <0>;
diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml
index 368d3db..5cfb9b9 100644
--- a/Documentation/devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml
+++ b/Documentation/devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml
@@ -76,7 +76,7 @@ examples:
#include <dt-bindings/clock/qcom,rpmh.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/interconnect/qcom,sm8250.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
display-subsystem@ae00000 {
compatible = "qcom,sm8250-mdss";
@@ -121,7 +121,7 @@ examples:
assigned-clock-rates = <19200000>;
operating-points-v2 = <&mdp_opp_table>;
- power-domains = <&rpmhpd SM8250_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
interrupt-parent = <&mdss>;
interrupts = <0>;
@@ -196,7 +196,7 @@ examples:
assigned-clock-parents = <&dsi0_phy 0>, <&dsi0_phy 1>;
operating-points-v2 = <&dsi_opp_table>;
- power-domains = <&rpmhpd SM8250_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
phys = <&dsi0_phy>;
phy-names = "dsi";
@@ -286,7 +286,7 @@ examples:
assigned-clock-parents = <&dsi1_phy 0>, <&dsi1_phy 1>;
operating-points-v2 = <&dsi_opp_table>;
- power-domains = <&rpmhpd SM8250_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
phys = <&dsi1_phy>;
phy-names = "dsi";
diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml
index 1205003..1a4e035 100644
--- a/Documentation/devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml
+++ b/Documentation/devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml
@@ -51,7 +51,7 @@ examples:
#include <dt-bindings/clock/qcom,gcc-sm8350.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/interconnect/qcom,sm8350.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
display-controller@ae01000 {
compatible = "qcom,sm8350-dpu";
@@ -76,7 +76,7 @@ examples:
assigned-clock-rates = <19200000>;
operating-points-v2 = <&mdp_opp_table>;
- power-domains = <&rpmhpd SM8350_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
interrupt-parent = <&mdss>;
interrupts = <0>;
diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml
index 79a226e..1056bed 100644
--- a/Documentation/devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml
+++ b/Documentation/devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml
@@ -75,7 +75,7 @@ examples:
#include <dt-bindings/clock/qcom,rpmh.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/interconnect/qcom,sm8350.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
display-subsystem@ae00000 {
compatible = "qcom,sm8350-mdss";
@@ -128,7 +128,7 @@ examples:
assigned-clock-rates = <19200000>;
operating-points-v2 = <&mdp_opp_table>;
- power-domains = <&rpmhpd SM8350_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
interrupt-parent = <&mdss>;
interrupts = <0>;
@@ -197,7 +197,7 @@ examples:
<&mdss_dsi0_phy 1>;
operating-points-v2 = <&dsi_opp_table>;
- power-domains = <&rpmhpd SM8350_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
phys = <&mdss_dsi0_phy>;
diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml
index 0d17ece..da3fd66 100644
--- a/Documentation/devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml
+++ b/Documentation/devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml
@@ -58,7 +58,7 @@ examples:
#include <dt-bindings/clock/qcom,gcc-sm8450.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/interconnect/qcom,sm8450.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
display-controller@ae01000 {
compatible = "qcom,sm8450-dpu";
@@ -83,7 +83,7 @@ examples:
assigned-clock-rates = <19200000>;
operating-points-v2 = <&mdp_opp_table>;
- power-domains = <&rpmhpd SM8450_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
interrupt-parent = <&mdss>;
interrupts = <0>;
diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml
index f26eb56..6dd21af 100644
--- a/Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml
+++ b/Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml
@@ -68,7 +68,7 @@ examples:
#include <dt-bindings/clock/qcom,rpmh.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/interconnect/qcom,sm8450.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
display-subsystem@ae00000 {
compatible = "qcom,sm8450-mdss";
@@ -122,7 +122,7 @@ examples:
assigned-clock-rates = <19200000>;
operating-points-v2 = <&mdp_opp_table>;
- power-domains = <&rpmhpd SM8450_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
interrupt-parent = <&mdss>;
interrupts = <0>;
@@ -202,7 +202,7 @@ examples:
assigned-clock-parents = <&dsi0_phy 0>, <&dsi0_phy 1>;
operating-points-v2 = <&dsi_opp_table>;
- power-domains = <&rpmhpd SM8450_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
phys = <&dsi0_phy>;
phy-names = "dsi";
@@ -297,7 +297,7 @@ examples:
assigned-clock-parents = <&dsi1_phy 0>, <&dsi1_phy 1>;
operating-points-v2 = <&dsi_opp_table>;
- power-domains = <&rpmhpd SM8450_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
phys = <&dsi1_phy>;
phy-names = "dsi";
diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml
index ff58a74..99908fb 100644
--- a/Documentation/devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml
+++ b/Documentation/devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml
@@ -57,7 +57,7 @@ examples:
#include <dt-bindings/clock/qcom,sm8550-dispcc.h>
#include <dt-bindings/clock/qcom,sm8550-gcc.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
display-controller@ae01000 {
compatible = "qcom,sm8550-dpu";
@@ -82,7 +82,7 @@ examples:
assigned-clock-rates = <19200000>;
operating-points-v2 = <&mdp_opp_table>;
- power-domains = <&rpmhpd SM8550_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
interrupt-parent = <&mdss>;
interrupts = <0>;
diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml
index 887be33..a464312 100644
--- a/Documentation/devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml
+++ b/Documentation/devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml
@@ -68,7 +68,7 @@ examples:
#include <dt-bindings/clock/qcom,rpmh.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/interconnect/qcom,sm8550-rpmh.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
display-subsystem@ae00000 {
compatible = "qcom,sm8550-mdss";
@@ -122,7 +122,7 @@ examples:
assigned-clock-rates = <19200000>;
operating-points-v2 = <&mdp_opp_table>;
- power-domains = <&rpmhpd SM8550_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
interrupt-parent = <&mdss>;
interrupts = <0>;
@@ -197,7 +197,7 @@ examples:
assigned-clock-parents = <&dsi0_phy 0>, <&dsi0_phy 1>;
operating-points-v2 = <&dsi_opp_table>;
- power-domains = <&rpmhpd SM8550_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
phys = <&dsi0_phy>;
phy-names = "dsi";
@@ -286,7 +286,7 @@ examples:
assigned-clock-parents = <&dsi1_phy 0>, <&dsi1_phy 1>;
operating-points-v2 = <&dsi_opp_table>;
- power-domains = <&rpmhpd SM8550_MMCX>;
+ power-domains = <&rpmhpd RPMHPD_MMCX>;
phys = <&dsi1_phy>;
phy-names = "dsi";
diff --git a/Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml b/Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml
index 7915dcd..f66033a 100644
--- a/Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml
+++ b/Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml
@@ -106,7 +106,7 @@ examples:
#include <dt-bindings/clock/qcom,videocc-sm8250.h>
#include <dt-bindings/interconnect/qcom,sm8250.h>
#include <dt-bindings/clock/qcom,gcc-sm8250.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
venus: video-codec@aa00000 {
compatible = "qcom,sm8250-venus";
@@ -114,7 +114,7 @@ examples:
interrupts = <GIC_SPI 174 IRQ_TYPE_LEVEL_HIGH>;
power-domains = <&videocc MVS0C_GDSC>,
<&videocc MVS0_GDSC>,
- <&rpmhpd SM8250_MX>;
+ <&rpmhpd RPMHPD_MX>;
power-domain-names = "venus", "vcodec0", "mx";
clocks = <&gcc GCC_VIDEO_AXI0_CLK>,
diff --git a/Documentation/devicetree/bindings/mmc/sdhci-msm.yaml b/Documentation/devicetree/bindings/mmc/sdhci-msm.yaml
index 6da28e6..80141eb 100644
--- a/Documentation/devicetree/bindings/mmc/sdhci-msm.yaml
+++ b/Documentation/devicetree/bindings/mmc/sdhci-msm.yaml
@@ -215,7 +215,7 @@ examples:
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/clock/qcom,gcc-sm8250.h>
#include <dt-bindings/clock/qcom,rpmh.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
sdhc_2: mmc@8804000 {
compatible = "qcom,sm8250-sdhci", "qcom,sdhci-msm-v5";
@@ -232,7 +232,7 @@ examples:
iommus = <&apps_smmu 0x4a0 0x0>;
qcom,dll-config = <0x0007642c>;
qcom,ddr-config = <0x80040868>;
- power-domains = <&rpmhpd SM8250_CX>;
+ power-domains = <&rpmhpd RPMHPD_CX>;
operating-points-v2 = <&sdhc2_opp_table>;
diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml
index af24f9a..9a04d19 100644
--- a/Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml
@@ -139,7 +139,7 @@ examples:
#include <dt-bindings/clock/qcom,rpmh.h>
#include <dt-bindings/interrupt-controller/irq.h>
#include <dt-bindings/mailbox/qcom-ipcc.h>
- #include <dt-bindings/power/qcom-rpmpd.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
remoteproc@30000000 {
compatible = "qcom,sm8450-adsp-pas";
@@ -160,8 +160,8 @@ examples:
memory-region = <&adsp_mem>;
- power-domains = <&rpmhpd SM8450_LCX>,
- <&rpmhpd SM8450_LMX>;
+ power-domains = <&rpmhpd RPMHPD_LCX>,
+ <&rpmhpd RPMHPD_LMX>;
power-domain-names = "lcx", "lmx";
qcom,qmp = <&aoss_qmp>;
--
2.7.4
On Thu, 27 Jul 2023 14:39:13 +0530, Rohit Agarwal wrote:
> Update the RPMHPD references with new bindings defined in rpmhpd.h
> for Qualcomm SoCs SM8[2345]50.
>
> Signed-off-by: Rohit Agarwal <[email protected]>
> ---
> Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml | 4 ++--
> Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml | 4 ++--
> Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml | 4 ++--
> Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml | 4 ++--
> Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml | 4 ++--
> Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml | 4 ++--
> Documentation/devicetree/bindings/clock/qcom,videocc.yaml | 4 ++--
> .../devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml | 4 ++--
> .../devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml | 8 ++++----
> .../devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml | 4 ++--
> .../devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml | 6 +++---
> .../devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml | 4 ++--
> .../devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml | 8 ++++----
> .../devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml | 4 ++--
> .../devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml | 8 ++++----
> Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml | 4 ++--
> Documentation/devicetree/bindings/mmc/sdhci-msm.yaml | 4 ++--
> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml | 6 +++---
> 18 files changed, 44 insertions(+), 44 deletions(-)
>
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dts:21:18: fatal error: dt-bindings/power/qcom,rpmhpd.h: No such file or directory
21 | #include <dt-bindings/power/qcom,rpmhpd.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [scripts/Makefile.lib:419: Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dtb] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1500: dt_binding_check] Error 2
make: *** [Makefile:234: __sub-make] Error 2
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/[email protected]
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
On 7/27/2023 4:46 PM, Rob Herring wrote:
> On Thu, 27 Jul 2023 14:39:13 +0530, Rohit Agarwal wrote:
>> Update the RPMHPD references with new bindings defined in rpmhpd.h
>> for Qualcomm SoCs SM8[2345]50.
>>
>> Signed-off-by: Rohit Agarwal <[email protected]>
>> ---
>> Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml | 4 ++--
>> Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml | 4 ++--
>> Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml | 4 ++--
>> Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml | 4 ++--
>> Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml | 4 ++--
>> Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml | 4 ++--
>> Documentation/devicetree/bindings/clock/qcom,videocc.yaml | 4 ++--
>> .../devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml | 4 ++--
>> .../devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml | 8 ++++----
>> .../devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml | 4 ++--
>> .../devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml | 6 +++---
>> .../devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml | 4 ++--
>> .../devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml | 8 ++++----
>> .../devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml | 4 ++--
>> .../devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml | 8 ++++----
>> Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml | 4 ++--
>> Documentation/devicetree/bindings/mmc/sdhci-msm.yaml | 4 ++--
>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml | 6 +++---
>> 18 files changed, 44 insertions(+), 44 deletions(-)
>>
> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> on your patch (DT_CHECKER_FLAGS is new in v5.13):
>
> yamllint warnings/errors:
>
> dtschema/dtc warnings/errors:
> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dts:21:18: fatal error: dt-bindings/power/qcom,rpmhpd.h: No such file or directory
> 21 | #include <dt-bindings/power/qcom,rpmhpd.h>
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[2]: *** [scripts/Makefile.lib:419: Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dtb] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1500: dt_binding_check] Error 2
> make: *** [Makefile:234: __sub-make] Error 2
>
> doc reference errors (make refcheckdocs):
>
> See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/[email protected]
>
> The base for the series is generally the latest rc1. A different dependency
> should be noted in *this* patch.
>
> If you already ran 'make dt_binding_check' and didn't see the above
> error(s), then make sure 'yamllint' is installed and dt-schema is up to
> date:
>
> pip3 install dtschema --upgrade
>
> Please check and re-submit after running the above command yourself. Note
> that DT_SCHEMA_FILES can be set to your schema file to speed up checking
> your schema. However, it must be unset to test all examples with your schema.
This should be ignored as the patch that creates the new header is
already applied.
Please follow this series
https://lore.kernel.org/all/[email protected]/
Thanks,
Rohit.
On 7/27/2023 5:57 PM, Krzysztof Kozlowski wrote:
> On 27/07/2023 14:21, Rohit Agarwal wrote:
>>>> https://lore.kernel.org/all/[email protected]/
>>> Please mention the dependency in patch changelog ---, so it is obvious
>>> for people applying it and also for the bot.
>> Sure. Will send a cover letter for this patch mentioning the changelogs
>> and will
>> keep the version as v2 since there no change at all in the patch.
> There is no need for cover letter for one patch.
Yes, I thought the same and thus didnt include the cover letter and
changelogs initially.
Can you please help where I can add the changelogs and the dependency link?
Thanks,
Rohit.
>
> Best regards,
> Krzysztof
>
On 7/27/2023 5:15 PM, Krzysztof Kozlowski wrote:
> On 27/07/2023 13:19, Rohit Agarwal wrote:
>> On 7/27/2023 4:46 PM, Rob Herring wrote:
>>> On Thu, 27 Jul 2023 14:39:13 +0530, Rohit Agarwal wrote:
>>>> Update the RPMHPD references with new bindings defined in rpmhpd.h
>>>> for Qualcomm SoCs SM8[2345]50.
>>>>
>>>> Signed-off-by: Rohit Agarwal <[email protected]>
>>>> ---
>>>> Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml | 4 ++--
>>>> Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml | 4 ++--
>>>> Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml | 4 ++--
>>>> Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml | 4 ++--
>>>> Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml | 4 ++--
>>>> Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml | 4 ++--
>>>> Documentation/devicetree/bindings/clock/qcom,videocc.yaml | 4 ++--
>>>> .../devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml | 4 ++--
>>>> .../devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml | 8 ++++----
>>>> .../devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml | 4 ++--
>>>> .../devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml | 6 +++---
>>>> .../devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml | 4 ++--
>>>> .../devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml | 8 ++++----
>>>> .../devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml | 4 ++--
>>>> .../devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml | 8 ++++----
>>>> Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml | 4 ++--
>>>> Documentation/devicetree/bindings/mmc/sdhci-msm.yaml | 4 ++--
>>>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml | 6 +++---
>>>> 18 files changed, 44 insertions(+), 44 deletions(-)
>>>>
>>> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
>>> on your patch (DT_CHECKER_FLAGS is new in v5.13):
>>>
>>> yamllint warnings/errors:
>>>
>>> dtschema/dtc warnings/errors:
>>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dts:21:18: fatal error: dt-bindings/power/qcom,rpmhpd.h: No such file or directory
>>> 21 | #include <dt-bindings/power/qcom,rpmhpd.h>
>>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> compilation terminated.
>>> make[2]: *** [scripts/Makefile.lib:419: Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dtb] Error 1
>>> make[2]: *** Waiting for unfinished jobs....
>>> make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1500: dt_binding_check] Error 2
>>> make: *** [Makefile:234: __sub-make] Error 2
>>>
>>> doc reference errors (make refcheckdocs):
>>>
>>> See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/[email protected]
>>>
>>> The base for the series is generally the latest rc1. A different dependency
>>> should be noted in *this* patch.
>>>
>>> If you already ran 'make dt_binding_check' and didn't see the above
>>> error(s), then make sure 'yamllint' is installed and dt-schema is up to
>>> date:
>>>
>>> pip3 install dtschema --upgrade
>>>
>>> Please check and re-submit after running the above command yourself. Note
>>> that DT_SCHEMA_FILES can be set to your schema file to speed up checking
>>> your schema. However, it must be unset to test all examples with your schema.
>> This should be ignored as the patch that creates the new header is
>> already applied.
>> Please follow this series
>>
>> https://lore.kernel.org/all/[email protected]/
> Please mention the dependency in patch changelog ---, so it is obvious
> for people applying it and also for the bot.
Sure. Will send a cover letter for this patch mentioning the changelogs
and will
keep the version as v2 since there no change at all in the patch.
Thanks,
Rohit.
> Best regards,
> Krzysztof
>
On 27/07/2023 14:21, Rohit Agarwal wrote:
>>> https://lore.kernel.org/all/[email protected]/
>> Please mention the dependency in patch changelog ---, so it is obvious
>> for people applying it and also for the bot.
> Sure. Will send a cover letter for this patch mentioning the changelogs
> and will
> keep the version as v2 since there no change at all in the patch.
There is no need for cover letter for one patch.
Best regards,
Krzysztof
On 7/27/2023 6:00 PM, Rohit Agarwal wrote:
>
> On 7/27/2023 5:57 PM, Krzysztof Kozlowski wrote:
>> On 27/07/2023 14:21, Rohit Agarwal wrote:
>>>>> https://lore.kernel.org/all/[email protected]/
>>>>>
>>>> Please mention the dependency in patch changelog ---, so it is obvious
>>>> for people applying it and also for the bot.
>>> Sure. Will send a cover letter for this patch mentioning the changelogs
>>> and will
>>> keep the version as v2 since there no change at all in the patch.
>> There is no need for cover letter for one patch.
> Yes, I thought the same and thus didnt include the cover letter and
> changelogs initially.
> Can you please help where I can add the changelogs and the dependency
> link?
Sorry! Got it.
Thanks,
Rohit.
>
> Thanks,
> Rohit.
>>
>> Best regards,
>> Krzysztof
>>
On 27/07/2023 13:19, Rohit Agarwal wrote:
>
> On 7/27/2023 4:46 PM, Rob Herring wrote:
>> On Thu, 27 Jul 2023 14:39:13 +0530, Rohit Agarwal wrote:
>>> Update the RPMHPD references with new bindings defined in rpmhpd.h
>>> for Qualcomm SoCs SM8[2345]50.
>>>
>>> Signed-off-by: Rohit Agarwal <[email protected]>
>>> ---
>>> Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml | 4 ++--
>>> Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml | 4 ++--
>>> Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml | 4 ++--
>>> Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml | 4 ++--
>>> Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml | 4 ++--
>>> Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml | 4 ++--
>>> Documentation/devicetree/bindings/clock/qcom,videocc.yaml | 4 ++--
>>> .../devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml | 4 ++--
>>> .../devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml | 8 ++++----
>>> .../devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml | 4 ++--
>>> .../devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml | 6 +++---
>>> .../devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml | 4 ++--
>>> .../devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml | 8 ++++----
>>> .../devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml | 4 ++--
>>> .../devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml | 8 ++++----
>>> Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml | 4 ++--
>>> Documentation/devicetree/bindings/mmc/sdhci-msm.yaml | 4 ++--
>>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml | 6 +++---
>>> 18 files changed, 44 insertions(+), 44 deletions(-)
>>>
>> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
>> on your patch (DT_CHECKER_FLAGS is new in v5.13):
>>
>> yamllint warnings/errors:
>>
>> dtschema/dtc warnings/errors:
>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dts:21:18: fatal error: dt-bindings/power/qcom,rpmhpd.h: No such file or directory
>> 21 | #include <dt-bindings/power/qcom,rpmhpd.h>
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> compilation terminated.
>> make[2]: *** [scripts/Makefile.lib:419: Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dtb] Error 1
>> make[2]: *** Waiting for unfinished jobs....
>> make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1500: dt_binding_check] Error 2
>> make: *** [Makefile:234: __sub-make] Error 2
>>
>> doc reference errors (make refcheckdocs):
>>
>> See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/[email protected]
>>
>> The base for the series is generally the latest rc1. A different dependency
>> should be noted in *this* patch.
>>
>> If you already ran 'make dt_binding_check' and didn't see the above
>> error(s), then make sure 'yamllint' is installed and dt-schema is up to
>> date:
>>
>> pip3 install dtschema --upgrade
>>
>> Please check and re-submit after running the above command yourself. Note
>> that DT_SCHEMA_FILES can be set to your schema file to speed up checking
>> your schema. However, it must be unset to test all examples with your schema.
> This should be ignored as the patch that creates the new header is
> already applied.
> Please follow this series
>
> https://lore.kernel.org/all/[email protected]/
Please mention the dependency in patch changelog ---, so it is obvious
for people applying it and also for the bot.
Best regards,
Krzysztof
On 27/07/2023 15:21, Rohit Agarwal wrote:
>
> On 7/27/2023 5:15 PM, Krzysztof Kozlowski wrote:
>> On 27/07/2023 13:19, Rohit Agarwal wrote:
>>> On 7/27/2023 4:46 PM, Rob Herring wrote:
>>>> On Thu, 27 Jul 2023 14:39:13 +0530, Rohit Agarwal wrote:
>>>>> Update the RPMHPD references with new bindings defined in rpmhpd.h
>>>>> for Qualcomm SoCs SM8[2345]50.
>>>>>
>>>>> Signed-off-by: Rohit Agarwal <[email protected]>
>>>>> ---
>>>>>
>>>>> Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml |
>>>>> 4 ++--
>>>>>
>>>>> Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml |
>>>>> 4 ++--
>>>>>
>>>>> Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml |
>>>>> 4 ++--
>>>>>
>>>>> Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml |
>>>>> 4 ++--
>>>>>
>>>>> Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml |
>>>>> 4 ++--
>>>>>
>>>>> Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml |
>>>>> 4 ++--
>>>>>
>>>>> Documentation/devicetree/bindings/clock/qcom,videocc.yaml |
>>>>> 4 ++--
>>>>>
>>>>> .../devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml |
>>>>> 4 ++--
>>>>>
>>>>> .../devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml |
>>>>> 8 ++++----
>>>>>
>>>>> .../devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml |
>>>>> 4 ++--
>>>>>
>>>>> .../devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml |
>>>>> 6 +++---
>>>>>
>>>>> .../devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml |
>>>>> 4 ++--
>>>>>
>>>>> .../devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml |
>>>>> 8 ++++----
>>>>>
>>>>> .../devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml |
>>>>> 4 ++--
>>>>>
>>>>> .../devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml |
>>>>> 8 ++++----
>>>>>
>>>>> Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml |
>>>>> 4 ++--
>>>>>
>>>>> Documentation/devicetree/bindings/mmc/sdhci-msm.yaml |
>>>>> 4 ++--
>>>>>
>>>>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml |
>>>>> 6 +++---
>>>>> 18 files changed, 44 insertions(+), 44 deletions(-)
>>>>>
>>>> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
>>>> on your patch (DT_CHECKER_FLAGS is new in v5.13):
>>>>
>>>> yamllint warnings/errors:
>>>>
>>>> dtschema/dtc warnings/errors:
>>>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dts:21:18: fatal error: dt-bindings/power/qcom,rpmhpd.h: No such file or directory
>>>> 21 | #include <dt-bindings/power/qcom,rpmhpd.h>
>>>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>> compilation terminated.
>>>> make[2]: *** [scripts/Makefile.lib:419:
>>>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dtb] Error 1
>>>> make[2]: *** Waiting for unfinished jobs....
>>>> make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1500:
>>>> dt_binding_check] Error 2
>>>> make: *** [Makefile:234: __sub-make] Error 2
>>>>
>>>> doc reference errors (make refcheckdocs):
>>>>
>>>> See
>>>> https://patchwork.ozlabs.org/project/devicetree-bindings/patch/[email protected]
>>>>
>>>> The base for the series is generally the latest rc1. A different
>>>> dependency
>>>> should be noted in *this* patch.
>>>>
>>>> If you already ran 'make dt_binding_check' and didn't see the above
>>>> error(s), then make sure 'yamllint' is installed and dt-schema is up to
>>>> date:
>>>>
>>>> pip3 install dtschema --upgrade
>>>>
>>>> Please check and re-submit after running the above command yourself.
>>>> Note
>>>> that DT_SCHEMA_FILES can be set to your schema file to speed up
>>>> checking
>>>> your schema. However, it must be unset to test all examples with
>>>> your schema.
>>> This should be ignored as the patch that creates the new header is
>>> already applied.
>>> Please follow this series
>>>
>>> https://lore.kernel.org/all/[email protected]/
>> Please mention the dependency in patch changelog ---, so it is obvious
>> for people applying it and also for the bot.
> Sure. Will send a cover letter for this patch mentioning the changelogs
> and will
> keep the version as v2 since there no change at all in the patch.
What would be the merge strategy? Even if you split it per subsystem, I
probably can not pick up display parts. Is there an immutable branch
with the new header? Otherwise I can either ack Bjorn picking up this
patch or it will have to wait for the next cycle.
>
> Thanks,
> Rohit.
>> Best regards,
>> Krzysztof
>>
--
With best wishes
Dmitry
On 7/27/2023 5:54 PM, Dmitry Baryshkov wrote:
> On 27/07/2023 15:21, Rohit Agarwal wrote:
>>
>> On 7/27/2023 5:15 PM, Krzysztof Kozlowski wrote:
>>> On 27/07/2023 13:19, Rohit Agarwal wrote:
>>>> On 7/27/2023 4:46 PM, Rob Herring wrote:
>>>>> On Thu, 27 Jul 2023 14:39:13 +0530, Rohit Agarwal wrote:
>>>>>> Update the RPMHPD references with new bindings defined in rpmhpd.h
>>>>>> for Qualcomm SoCs SM8[2345]50.
>>>>>>
>>>>>> Signed-off-by: Rohit Agarwal <[email protected]>
>>>>>> ---
>>>>>> Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml |
>>>>>> 4 ++--
>>>>>> Documentation/devicetree/bindings/clock/qcom,sm8350-videocc.yaml
>>>>>> | 4 ++--
>>>>>> Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml |
>>>>>> 4 ++--
>>>>>> Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml |
>>>>>> 4 ++--
>>>>>> Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
>>>>>> | 4 ++--
>>>>>> Documentation/devicetree/bindings/clock/qcom,sm8550-dispcc.yaml |
>>>>>> 4 ++--
>>>>>> Documentation/devicetree/bindings/clock/qcom,videocc.yaml | 4 ++--
>>>>>> .../devicetree/bindings/display/msm/qcom,sm8250-dpu.yaml | 4 ++--
>>>>>> .../devicetree/bindings/display/msm/qcom,sm8250-mdss.yaml | 8
>>>>>> ++++----
>>>>>> .../devicetree/bindings/display/msm/qcom,sm8350-dpu.yaml | 4 ++--
>>>>>> .../devicetree/bindings/display/msm/qcom,sm8350-mdss.yaml | 6 +++---
>>>>>> .../devicetree/bindings/display/msm/qcom,sm8450-dpu.yaml | 4 ++--
>>>>>> .../devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml | 8
>>>>>> ++++----
>>>>>> .../devicetree/bindings/display/msm/qcom,sm8550-dpu.yaml | 4 ++--
>>>>>> .../devicetree/bindings/display/msm/qcom,sm8550-mdss.yaml | 8
>>>>>> ++++----
>>>>>> Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml |
>>>>>> 4 ++--
>>>>>> Documentation/devicetree/bindings/mmc/sdhci-msm.yaml | 4 ++--
>>>>>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml
>>>>>> | 6 +++---
>>>>>> 18 files changed, 44 insertions(+), 44 deletions(-)
>>>>>>
>>>>> My bot found errors running 'make DT_CHECKER_FLAGS=-m
>>>>> dt_binding_check'
>>>>> on your patch (DT_CHECKER_FLAGS is new in v5.13):
>>>>>
>>>>> yamllint warnings/errors:
>>>>>
>>>>> dtschema/dtc warnings/errors:
>>>>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dts:21:18:
>>>>> fatal error: dt-bindings/power/qcom,rpmhpd.h: No such file or
>>>>> directory
>>>>> 21 | #include <dt-bindings/power/qcom,rpmhpd.h>
>>>>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>> compilation terminated.
>>>>> make[2]: *** [scripts/Makefile.lib:419:
>>>>> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.example.dtb]
>>>>> Error 1
>>>>> make[2]: *** Waiting for unfinished jobs....
>>>>> make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1500:
>>>>> dt_binding_check] Error 2
>>>>> make: *** [Makefile:234: __sub-make] Error 2
>>>>>
>>>>> doc reference errors (make refcheckdocs):
>>>>>
>>>>> See
>>>>> https://patchwork.ozlabs.org/project/devicetree-bindings/patch/[email protected]
>>>>>
>>>>> The base for the series is generally the latest rc1. A different
>>>>> dependency
>>>>> should be noted in *this* patch.
>>>>>
>>>>> If you already ran 'make dt_binding_check' and didn't see the above
>>>>> error(s), then make sure 'yamllint' is installed and dt-schema is
>>>>> up to
>>>>> date:
>>>>>
>>>>> pip3 install dtschema --upgrade
>>>>>
>>>>> Please check and re-submit after running the above command
>>>>> yourself. Note
>>>>> that DT_SCHEMA_FILES can be set to your schema file to speed up
>>>>> checking
>>>>> your schema. However, it must be unset to test all examples with
>>>>> your schema.
>>>> This should be ignored as the patch that creates the new header is
>>>> already applied.
>>>> Please follow this series
>>>>
>>>> https://lore.kernel.org/all/[email protected]/
>>>>
>>> Please mention the dependency in patch changelog ---, so it is obvious
>>> for people applying it and also for the bot.
>> Sure. Will send a cover letter for this patch mentioning the
>> changelogs and will
>> keep the version as v2 since there no change at all in the patch.
>
> What would be the merge strategy? Even if you split it per subsystem,
> I probably can not pick up display parts. Is there an immutable branch
> with the new header? Otherwise I can either ack Bjorn picking up this
> patch or it will have to wait for the next cycle.
The reason why I sent it as a single patch is that maintainers cannot
pick it up separately. So since Bjorn already have the new header change
included in the tree, it would be better if he picks it up.
Thanks,
Rohit.
>
>>
>> Thanks,
>> Rohit.
>>> Best regards,
>>> Krzysztof
>>>
>