Commit 5342f1df authored by Stephan Gerhold's avatar Stephan Gerhold Committed by Bjorn Andersson

arm64: dts: qcom: msm8916: Drop qcom,tcsr-mutex syscon

The hwlock device node does not (directly) use memory resources
of the SoC, so we should move it outside the "soc" node.

However, as of commit 7a1e6fb1 ("hwspinlock: qcom: Allow mmio usage
in addition to syscon") we can now assign the memory region directly
to the hwlock device node. This works because the register space
used by it is actually separate and not used by any other components.
Signed-off-by: default avatarStephan Gerhold <stephan@gerhold.net>
Link: https://lore.kernel.org/r/20200915071221.72895-7-stephan@gerhold.netSigned-off-by: default avatarBjorn Andersson <bjorn.andersson@linaro.org>
parent dd5f6c73
...@@ -458,9 +458,10 @@ gcc: clock-controller@1800000 { ...@@ -458,9 +458,10 @@ gcc: clock-controller@1800000 {
reg = <0x1800000 0x80000>; reg = <0x1800000 0x80000>;
}; };
tcsr_mutex_regs: syscon@1905000 { tcsr_mutex: hwlock@1905000 {
compatible = "syscon"; compatible = "qcom,tcsr-mutex";
reg = <0x1905000 0x20000>; reg = <0x1905000 0x20000>;
#hwlock-cells = <1>;
}; };
tcsr: syscon@1937000 { tcsr: syscon@1937000 {
...@@ -468,12 +469,6 @@ tcsr: syscon@1937000 { ...@@ -468,12 +469,6 @@ tcsr: syscon@1937000 {
reg = <0x1937000 0x30000>; reg = <0x1937000 0x30000>;
}; };
tcsr_mutex: hwlock {
compatible = "qcom,tcsr-mutex";
syscon = <&tcsr_mutex_regs 0 0x1000>;
#hwlock-cells = <1>;
};
rpm_msg_ram: memory@60000 { rpm_msg_ram: memory@60000 {
compatible = "qcom,rpm-msg-ram"; compatible = "qcom,rpm-msg-ram";
reg = <0x60000 0x8000>; reg = <0x60000 0x8000>;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment