arm64: dts: ti: k3-am64: Only set UART baud for used ports
Subsystems (2)
PATCH 1/2 arm64: dts: ti: k3-am64: Only set UART baud for used ports
As the binding for "current-speed" states, this should only be used when the baud rate of an attached device cannot be detected. This is the case for our attached on-board USB-to-UART converter used for early kernel console. For all other unconnected/disabled ports this can be configured in userspace later, DT is not the place for device configuration, especially when there are already standard ways to set serial baud in userspace.
Remove setting baud for all disabled serial ports and move setting it for the couple enabled ports down into the board files.
--- arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 7 ------- arch/arm64/boot/dts/ti/k3-am64-mcu.dtsi | 2 -- arch/arm64/boot/dts/ti/k3-am642-evm.dts | 1 + arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts | 2 ++ arch/arm64/boot/dts/ti/k3-am642-sk.dts | 1 + 5 files changed, 4 insertions(+), 9 deletions(-)
arch/arm64/boot/dts/ti/k3-am64-main.dtsi +0 -7
@@ -377,7 +377,6 @@ main_uart0: serial@2800000 { reg = <0x00 0x02800000 0x00 0x100>; interrupts = <GIC_SPI 178 IRQ_TYPE_LEVEL_HIGH>; clock-frequency = <48000000>; - current-speed = <115200>; power-domains = <&k3_pds 146 TI_SCI_PD_EXCLUSIVE>; clocks = <&k3_clks 146 0>; clock-names = "fclk";
@@ -389,7 +388,6 @@ main_uart1: serial@2810000 { reg = <0x00 0x02810000 0x00 0x100>; interrupts = <GIC_SPI 179 IRQ_TYPE_LEVEL_HIGH>; clock-frequency = <48000000>; - current-speed = <115200>; power-domains = <&k3_pds 152 TI_SCI_PD_EXCLUSIVE>; clocks = <&k3_clks 152 0>; clock-names = "fclk";
@@ -401,7 +399,6 @@ main_uart2: serial@2820000 { reg = <0x00 0x02820000 0x00 0x100>; interrupts = <GIC_SPI 180 IRQ_TYPE_LEVEL_HIGH>; clock-frequency = <48000000>; - current-speed = <115200>; power-domains = <&k3_pds 153 TI_SCI_PD_EXCLUSIVE>; clocks = <&k3_clks 153 0>; clock-names = "fclk";
@@ -413,7 +410,6 @@ main_uart3: serial@2830000 { reg = <0x00 0x02830000 0x00 0x100>; interrupts = <GIC_SPI 181 IRQ_TYPE_LEVEL_HIGH>; clock-frequency = <48000000>; - current-speed = <115200>; power-domains = <&k3_pds 154 TI_SCI_PD_EXCLUSIVE>; clocks = <&k3_clks 154 0>; clock-names = "fclk";
@@ -425,7 +421,6 @@ main_uart4: serial@2840000 { reg = <0x00 0x02840000 0x00 0x100>; interrupts = <GIC_SPI 182 IRQ_TYPE_LEVEL_HIGH>; clock-frequency = <48000000>; - current-speed = <115200>; power-domains = <&k3_pds 155 TI_SCI_PD_EXCLUSIVE>; clocks = <&k3_clks 155 0>; clock-names = "fclk";
@@ -437,7 +432,6 @@ main_uart5: serial@2850000 { reg = <0x00 0x02850000 0x00 0x100>; interrupts = <GIC_SPI 183 IRQ_TYPE_LEVEL_HIGH>; clock-frequency = <48000000>; - current-speed = <115200>; power-domains = <&k3_pds 156 TI_SCI_PD_EXCLUSIVE>; clocks = <&k3_clks 156 0>; clock-names = "fclk";
@@ -449,7 +443,6 @@ main_uart6: serial@2860000 { reg = <0x00 0x02860000 0x00 0x100>; interrupts = <GIC_SPI 184 IRQ_TYPE_LEVEL_HIGH>; clock-frequency = <48000000>; - current-speed = <115200>; power-domains = <&k3_pds 158 TI_SCI_PD_EXCLUSIVE>; clocks = <&k3_clks 158 0>; clock-names = "fclk";
arch/arm64/boot/dts/ti/k3-am64-mcu.dtsi +0 -2
@@ -55,7 +55,6 @@ mcu_uart0: serial@4a00000 { compatible = "ti,am64-uart", "ti,am654-uart"; reg = <0x00 0x04a00000 0x00 0x100>; interrupts = <GIC_SPI 185 IRQ_TYPE_LEVEL_HIGH>; - current-speed = <115200>; power-domains = <&k3_pds 149 TI_SCI_PD_EXCLUSIVE>; clocks = <&k3_clks 149 0>; clock-names = "fclk";
@@ -66,7 +65,6 @@ mcu_uart1: serial@4a10000 { compatible = "ti,am64-uart", "ti,am654-uart"; reg = <0x00 0x04a10000 0x00 0x100>; interrupts = <GIC_SPI 186 IRQ_TYPE_LEVEL_HIGH>; - current-speed = <115200>; power-domains = <&k3_pds 160 TI_SCI_PD_EXCLUSIVE>; clocks = <&k3_clks 160 0>; clock-names = "fclk";
arch/arm64/boot/dts/ti/k3-am642-evm.dts +1 -0
@@ -375,6 +375,7 @@ &main_uart0 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&main_uart0_pins_default>; + current-speed = <115200>; }; /* main_uart1 is reserved for firmware usage */
arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts +2 -0
@@ -230,6 +230,7 @@ &main_uart0 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&main_uart0_pins_default>; + current-speed = <115200>; }; &main_uart1 {
@@ -237,6 +238,7 @@ &main_uart1 { pinctrl-names = "default"; pinctrl-0 = <&main_uart1_pins_default>; uart-has-rtscts; + current-speed = <115200>; }; &sdhci1 {
arch/arm64/boot/dts/ti/k3-am642-sk.dts +1 -0
@@ -369,6 +369,7 @@ &main_uart0 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&main_uart0_pins_default>; + current-speed = <115200>; }; &main_uart1 {
Signature · 1 line
2.39.2
PATCH 2/2 arm64: dts: ti: k3-am64: Use phandle to stdout UART node
Using a phandle makes it clear which UART we are choosing without needing to resolve through an alias first.
Especially useful for boards like the TI J721s2-EVM where the alias is "serial2" but it actually resolves to the 8th UART instance(main_uart8).
--- arch/arm64/boot/dts/ti/k3-am642-evm.dts | 2 +- arch/arm64/boot/dts/ti/k3-am642-sk.dts | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
arch/arm64/boot/dts/ti/k3-am642-evm.dts +1 -1
@@ -17,7 +17,7 @@ / { model = "Texas Instruments AM642 EVM"; chosen { - stdout-path = "serial2:115200n8"; + stdout-path = &main_uart0; }; aliases {
arch/arm64/boot/dts/ti/k3-am642-sk.dts +1 -1
@@ -17,7 +17,7 @@ / { model = "Texas Instruments AM642 SK"; chosen { - stdout-path = "serial2:115200n8"; + stdout-path = &main_uart0; }; aliases {
Signature · 1 line
2.39.2
Hi Andrew Davis,
Quoted 9 lines · Andrew Davis
As the binding for "current-speed" states, this should only be used when the baud rate of an attached device cannot be detected. This is the case for our attached on-board USB-to-UART converter used for early kernel console. For all other unconnected/disabled ports this can be configured in userspace later, DT is not the place for device configuration, especially when there are already standard ways to set serial baud in userspace.
[...]
I have applied the following to branch ti-k3-dts-next on [1]. Thank you!
[1/2] arm64: dts: ti: k3-am64: Only set UART baud for used ports
commit: 27f98f3eca7334fec668ec637ed5e0514458bba8
[2/2] arm64: dts: ti: k3-am64: Use phandle to stdout UART node
commit: 6b343136388fe1ef5837e45ab921705de76665eeAll being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh