Commit 9e5c45a5 authored by Luca Weiss's avatar Luca Weiss Committed by Bjorn Andersson

arm64: dts: qcom: sm6350: Fix naming of uart9

The uart9 was previously mistakenly called uart2. Fix this.
Signed-off-by: default avatarLuca Weiss <luca.weiss@fairphone.com>
Signed-off-by: default avatarBjorn Andersson <bjorn.andersson@linaro.org>
Link: https://lore.kernel.org/r/20220408114205.234635-1-luca.weiss@fairphone.com
parent e7773dbc
...@@ -529,13 +529,13 @@ qupv3_id_1: geniqup@9c0000 { ...@@ -529,13 +529,13 @@ qupv3_id_1: geniqup@9c0000 {
ranges; ranges;
status = "disabled"; status = "disabled";
uart2: serial@98c000 { uart9: serial@98c000 {
compatible = "qcom,geni-debug-uart"; compatible = "qcom,geni-debug-uart";
reg = <0 0x98c000 0 0x4000>; reg = <0 0x98c000 0 0x4000>;
clock-names = "se"; clock-names = "se";
clocks = <&gcc GCC_QUPV3_WRAP1_S3_CLK>; clocks = <&gcc GCC_QUPV3_WRAP1_S3_CLK>;
pinctrl-names = "default"; pinctrl-names = "default";
pinctrl-0 = <&qup_uart2_default>; pinctrl-0 = <&qup_uart9_default>;
interrupts = <GIC_SPI 356 IRQ_TYPE_LEVEL_HIGH>; interrupts = <GIC_SPI 356 IRQ_TYPE_LEVEL_HIGH>;
status = "disabled"; status = "disabled";
}; };
...@@ -974,7 +974,7 @@ tlmm: pinctrl@f100000 { ...@@ -974,7 +974,7 @@ tlmm: pinctrl@f100000 {
#interrupt-cells = <2>; #interrupt-cells = <2>;
gpio-ranges = <&tlmm 0 0 157>; gpio-ranges = <&tlmm 0 0 157>;
qup_uart2_default: qup-uart2-default { qup_uart9_default: qup-uart9-default {
pins = "gpio25", "gpio26"; pins = "gpio25", "gpio26";
function = "qup13_f2"; function = "qup13_f2";
drive-strength = <2>; drive-strength = <2>;
......
...@@ -23,7 +23,7 @@ / { ...@@ -23,7 +23,7 @@ / {
qcom,board-id = <8 32>; qcom,board-id = <8 32>;
aliases { aliases {
serial0 = &uart2; serial0 = &uart9;
}; };
chosen { chosen {
...@@ -332,7 +332,7 @@ &tlmm { ...@@ -332,7 +332,7 @@ &tlmm {
gpio-reserved-ranges = <13 4>, <56 2>; gpio-reserved-ranges = <13 4>, <56 2>;
}; };
&uart2 { &uart9 {
status = "okay"; status = "okay";
}; };
......
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