The TCSR mutex bindings allow device to be described only with address
space (so it uses MMIO, not syscon regmap).  This seems reasonable as
TCSR mutex is actually a dedicated IO address space and it also fixes DT
schema checks:
  qcom/msm8996-xiaomi-natrium.dtb: hwlock: 'reg' is a required property
  qcom/msm8996-xiaomi-natrium.dtb: hwlock: 'syscon' does not match any of the regexes: 'pinctrl-[0-9]+'
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Konrad Dybcio <konrad.dybcio@somainline.org>
Signed-off-by: Bjorn Andersson <andersson@kernel.org>
Link: https://lore.kernel.org/r/20220819083209.50844-4-krzysztof.kozlowski@linaro.org
 
                };
        };
 
-       tcsr_mutex: hwlock {
-               compatible = "qcom,tcsr-mutex";
-               syscon = <&tcsr_mutex_regs 0 0x1000>;
-               #hwlock-cells = <1>;
-       };
-
        memory@80000000 {
                device_type = "memory";
                /* We expect the bootloader to fill in the reg */
                                 <&rpmcc RPM_SMD_PCNOC_A_CLK>;
                };
 
-               tcsr_mutex_regs: syscon@740000 {
-                       compatible = "syscon";
+               tcsr_mutex: hwlock@740000 {
+                       compatible = "qcom,tcsr-mutex";
                        reg = <0x00740000 0x20000>;
+                       #hwlock-cells = <1>;
                };
 
                tcsr_1: sycon@760000 {