Commit 7908dcc8 authored by Krzysztof Kozlowski's avatar Krzysztof Kozlowski Committed by Bjorn Andersson

arm64: dts: qcom: sdm630: order regs according to bindings

The CAMSS DTSI device node, which came after the bindings were merged,
got the regs ordered differently then specified in the bindings:

  sdm636-sony-xperia-ganges-mermaid.dtb: camss@ca00000: reg-names:0: 'csi_clk_mux' was expected

Reordering them to match bindings should not cause ABI issues, because
the driver relies on names, not ordering.
Signed-off-by: default avatarKrzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: default avatarBjorn Andersson <bjorn.andersson@linaro.org>
Link: https://lore.kernel.org/r/20220509144714.144154-3-krzysztof.kozlowski@linaro.org
parent e8881372
...@@ -1846,32 +1846,32 @@ pil-reloc@94c { ...@@ -1846,32 +1846,32 @@ pil-reloc@94c {
camss: camss@ca00000 { camss: camss@ca00000 {
compatible = "qcom,sdm660-camss"; compatible = "qcom,sdm660-camss";
reg = <0x0c824000 0x1000>, reg = <0x0ca00020 0x10>,
<0x0ca30000 0x100>,
<0x0ca30400 0x100>,
<0x0ca30800 0x100>,
<0x0ca30c00 0x100>,
<0x0c824000 0x1000>,
<0x0ca00120 0x4>, <0x0ca00120 0x4>,
<0x0c825000 0x1000>, <0x0c825000 0x1000>,
<0x0ca00124 0x4>, <0x0ca00124 0x4>,
<0x0c826000 0x1000>, <0x0c826000 0x1000>,
<0x0ca00128 0x4>, <0x0ca00128 0x4>,
<0x0ca30000 0x100>,
<0x0ca30400 0x100>,
<0x0ca30800 0x100>,
<0x0ca30c00 0x100>,
<0x0ca31000 0x500>, <0x0ca31000 0x500>,
<0x0ca00020 0x10>,
<0x0ca10000 0x1000>, <0x0ca10000 0x1000>,
<0x0ca14000 0x1000>; <0x0ca14000 0x1000>;
reg-names = "csiphy0", reg-names = "csi_clk_mux",
"csid0",
"csid1",
"csid2",
"csid3",
"csiphy0",
"csiphy0_clk_mux", "csiphy0_clk_mux",
"csiphy1", "csiphy1",
"csiphy1_clk_mux", "csiphy1_clk_mux",
"csiphy2", "csiphy2",
"csiphy2_clk_mux", "csiphy2_clk_mux",
"csid0",
"csid1",
"csid2",
"csid3",
"ispif", "ispif",
"csi_clk_mux",
"vfe0", "vfe0",
"vfe1"; "vfe1";
interrupts = <GIC_SPI 78 IRQ_TYPE_EDGE_RISING>, interrupts = <GIC_SPI 78 IRQ_TYPE_EDGE_RISING>,
......
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