[PATCH v1 10/23] arm: dts: layerscape: nbxv3: enable UART0..UART3

Vincent Jardin <[email protected]>
Newsgroups org.u-boot-project.lists.u-boot
Message-ID <[email protected]>
&uart0 (LX2160ARM UART1, MMIO 0x021c0000) is the console. The
remaining three (&uart1..&uart3) are available for applications
at the U-Boot prompt.

Numbering note: the LX2160A has four PL011 UARTs on chip. The
reference manual labels them 1 indexed (UART1..UART4); the device
tree is 0 indexed (&uart0..&uart3).
The mapping is constant across the family:

 - &uart0   LX2160ARM UART1   MMIO 0x021c0000   (console)
 - &uart1   LX2160ARM UART2   MMIO 0x021d0000
 - &uart2   LX2160ARM UART3   MMIO 0x021e0000
 - &uart3   LX2160ARM UART4   MMIO 0x021f0000

TF-A also uses &uart0 for its own boot log.

U-Boot console is at 115200 8N1.

Signed-off-by: Vincent Jardin <[email protected]>
---

 arch/arm/dts/fsl-lx2160a-nbxv3.dts | 20 ++++++++++++++++++++
 configs/nbxv3_tfa_defconfig        |  1 +
 2 files changed, 21 insertions(+)

diff --git a/arch/arm/dts/fsl-lx2160a-nbxv3.dts b/arch/arm/dts/fsl-lx2160a-nbxv3.dts
index 9dcc1bf1d5e..9b79d2c3253 100644
--- a/arch/arm/dts/fsl-lx2160a-nbxv3.dts
+++ b/arch/arm/dts/fsl-lx2160a-nbxv3.dts
@@ -13,6 +13,26 @@
 / {
 	model = "Free Mobile Nodebox v3 CPU Module (LX2160A)";
 	compatible = "freemobile,nbxv3", "fsl,lx2160a";
+
+	aliases {
+		serial0 = &uart0;
+	};
+};
+
+&uart0 {
+	status = "okay";
+};
+
+&uart1 {
+	status = "okay";
+};
+
+&uart2 {
+	status = "okay";
+};
+
+&uart3 {
+	status = "okay";
 };
 
 /*
diff --git a/configs/nbxv3_tfa_defconfig b/configs/nbxv3_tfa_defconfig
index cb6043f3278..6d55a808a76 100644
--- a/configs/nbxv3_tfa_defconfig
+++ b/configs/nbxv3_tfa_defconfig
@@ -20,6 +20,7 @@ CONFIG_MP=y
 CONFIG_DYNAMIC_SYS_CLK_FREQ=y
 # CONFIG_EFI_LOADER is not set
 CONFIG_OF_BOARD_SETUP=y
+CONFIG_OF_STDOUT_VIA_ALIAS=y
 CONFIG_SYS_PBSIZE=532
 # CONFIG_ID_EEPROM is not set
 CONFIG_RESET_PHY_R=y
-- 
2.43.0
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.