From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: rockchip: add bootargs setting the correct serial console
Date: Mon, 04 Aug 2014 19:00:07 +0200 [thread overview]
Message-ID: <1539097.4Cm43oOanj@diego> (raw)
In-Reply-To: <5084600.YbBVvXy6Ug@diego>
Uart2 seems to be designated debug uart for all Rockchip platforms.
On all rk30xx and rk31xx boards I've seen so far, this uart was used
for the console and the rk3288 TRM even describes it as debug uart.
Thus add it to the core SoC dtsi files to not duplicate the same
information on every board.
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
---
This makes a multi_v7_defconfig-based kernel start sucessfully on my
rk3188-radxarock and rk3288-evb
arch/arm/boot/dts/rk3288.dtsi | 4 ++++
arch/arm/boot/dts/rk3xxx.dtsi | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index e7cb008..3950bad 100644
--- a/arch/arm/boot/dts/rk3288.dtsi
+++ b/arch/arm/boot/dts/rk3288.dtsi
@@ -36,6 +36,10 @@
serial4 = &uart4;
};
+ chosen {
+ bootargs = "console=ttyS2,115200";
+ };
+
cpus {
#address-cells = <1>;
#size-cells = <0>;
diff --git a/arch/arm/boot/dts/rk3xxx.dtsi b/arch/arm/boot/dts/rk3xxx.dtsi
index 8caf85d..9eeb6cb 100644
--- a/arch/arm/boot/dts/rk3xxx.dtsi
+++ b/arch/arm/boot/dts/rk3xxx.dtsi
@@ -28,6 +28,10 @@
i2c4 = &i2c4;
};
+ chosen {
+ bootargs = "console=ttyS2,115200";
+ };
+
xin24m: oscillator {
compatible = "fixed-clock";
clock-frequency = <24000000>;
--
2.0.1
next prev parent reply other threads:[~2014-08-04 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 16:59 [PATCH 1/2] ARM: multi_v7_defconfig: Enable ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND Heiko Stübner
2014-08-04 17:00 ` Heiko Stübner [this message]
2014-08-04 17:29 ` [PATCH 2/2] ARM: dts: rockchip: add bootargs setting the correct serial console Arnd Bergmann
2014-08-05 12:53 ` Heiko Stübner
2014-08-05 14:53 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1539097.4Cm43oOanj@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).