From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: Define stdout-path property for Spring board
Date: Mon, 16 Mar 2015 12:05:44 +0100 [thread overview]
Message-ID: <5506B908.1060007@suse.de> (raw)
In-Reply-To: <1426501710-24177-4-git-send-email-javier.martinez@collabora.co.uk>
Hi,
Am 16.03.2015 um 11:28 schrieb Javier Martinez Canillas:
> The kernel can use as the default console a serial port if is defined
"The kernel can use a serial port as the default console if it's defined
..."
> as stdout device in the Device Tree.
>
> This allows a board to be booted without the need of having a console
> parameter in the kernel command line.
>
> Currently the Spring DTS has bootargs in the /chosen node and this is
> kept since users that don't have a serial console on this board might
> be using it to have the boot log shown in the display. This will have
> more precedence than the stdout-path but it's fine since is only used
"since it's"
> when CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND is enabled.
>
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> ---
> arch/arm/boot/dts/exynos5250-spring.dts | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/exynos5250-spring.dts b/arch/arm/boot/dts/exynos5250-spring.dts
> index f02775487cd4..b9ec763a5602 100644
> --- a/arch/arm/boot/dts/exynos5250-spring.dts
> +++ b/arch/arm/boot/dts/exynos5250-spring.dts
> @@ -25,6 +25,7 @@
>
> chosen {
> bootargs = "console=tty1";
> + stdout-path = "serial3:115200n8";
Is this a guess or did you verify that against some schematics?
> };
>
> gpio-keys {
Assuming that bootargs still work,
Reviewed-by: Andreas F?rber <afaerber@suse.de>
I do wonder why this mechanism could not point to the same location as
bootargs? ("dp-controller"?) The device does not even have screws for
opening it, so accessing the serial port is highly theoretical.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2015-03-16 11:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 10:28 [PATCH 0/3] ARM: dts: Define stdout-patch for Exynos Chromebooks Javier Martinez Canillas
2015-03-16 10:28 ` [PATCH 1/3] ARM: dts: Define stdout-path property for Peach boards Javier Martinez Canillas
2015-03-16 10:28 ` [PATCH 2/3] ARM: dts: Define stdout-path property for Snow board Javier Martinez Canillas
2015-03-16 10:28 ` [PATCH 3/3] ARM: dts: Define stdout-path property for Spring board Javier Martinez Canillas
2015-03-16 11:05 ` Andreas Färber [this message]
2015-03-16 11:28 ` Javier Martinez Canillas
2015-03-17 15:29 ` Kukjin Kim
2015-03-17 1:51 ` [PATCH 0/3] ARM: dts: Define stdout-patch for Exynos Chromebooks Kukjin Kim
2015-03-17 5:27 ` Arnd Bergmann
2015-03-17 15:28 ` Kukjin Kim
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=5506B908.1060007@suse.de \
--to=afaerber@suse.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).