summaryrefslogtreecommitdiffstats
path: root/arch/arm/boot/dts/bcm94709.dts
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2017-03-15 18:03:27 +0100
committerFlorian Fainelli <f.fainelli@gmail.com>2017-03-22 09:48:24 -0700
commit5be82d0475941dc96eeeee3c754baf48365f7bf5 (patch)
tree78df30c6fbcba39374bcf224ba503d3f8a9d3233 /arch/arm/boot/dts/bcm94709.dts
parentec73ab6b4d2acb8f5fd9344e9491c62973904a7e (diff)
downloadblackbird-obmc-linux-5be82d0475941dc96eeeee3c754baf48365f7bf5.tar.gz
blackbird-obmc-linux-5be82d0475941dc96eeeee3c754baf48365f7bf5.zip
ARM: dts: BCM5301X: Specify serial console params in dtsi files
So far every Northstar device we have seen was using the same serial console params (115200n8). It probably make the most sense to put it in some proper dtsi files instead of repeating over and over for every single device. As different boards may use different bootloaders it seems the safest idea is to use board specific dtsi files. Just in case some vendor decides to use different UART (parameters) this can be always easily overwritten. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Diffstat (limited to 'arch/arm/boot/dts/bcm94709.dts')
-rw-r--r--arch/arm/boot/dts/bcm94709.dts8
1 files changed, 0 insertions, 8 deletions
diff --git a/arch/arm/boot/dts/bcm94709.dts b/arch/arm/boot/dts/bcm94709.dts
index 95e8be65f2f1..c37616c67edc 100644
--- a/arch/arm/boot/dts/bcm94709.dts
+++ b/arch/arm/boot/dts/bcm94709.dts
@@ -38,14 +38,6 @@
model = "NorthStar SVK (BCM94709)";
compatible = "brcm,bcm94709", "brcm,bcm4709", "brcm,bcm4708";
- aliases {
- serial0 = &uart0;
- };
-
- chosen {
- stdout-path = "serial0:115200n8";
- };
-
memory {
reg = <0x00000000 0x08000000>;
};
OpenPOWER on IntegriCloud