From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: Don't set the default console to ttyAMA0
Date: Thu, 18 Feb 2016 15:15:21 +0800 [thread overview]
Message-ID: <20160218151521.66e0cbf7@xhacker> (raw)
In-Reply-To: <1455727422-10733-1-git-send-email-jonathanh@nvidia.com>
Dear Jon,
On Wed, 17 Feb 2016 16:43:42 +0000 Jon Hunter wrote:
> When booting Tegra210 with a minimal rootfs it may not be necessary to
> specify any boot parameters via the kernel command line as information
> for console is described via the "stdout-path" node the device-tree
> blob. However, when there are no boot parameter specified, no output is
> seen on the console in the case of Tegra210 and this is because the
> default command line in the ARM64 defconfig specifies the console as
> ttyAMA0 which takes precedence over the "stdout-path" node from
> device-tree.
>
> ttyAMAx is used for AMBA PL011 serial ports, but not all ARM64 platforms
> use this serial driver. Therefore, remove the default command line
> entry from the ARM64 defconfig to ensure that ttyAMA0 does not get set
> as the default console if no kernel command line is specified.
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
We need this patch as well. Thanks
Tested-by: Jisheng Zhang <jszhang@marvell.com>
> ---
> arch/arm64/configs/defconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index d21631760ec7..caecb66188be 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -64,7 +64,6 @@ CONFIG_KSM=y
> CONFIG_TRANSPARENT_HUGEPAGE=y
> CONFIG_CMA=y
> CONFIG_XEN=y
> -CONFIG_CMDLINE="console=ttyAMA0"
> # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
> CONFIG_COMPAT=y
> CONFIG_CPU_IDLE=y
next prev parent reply other threads:[~2016-02-18 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 16:43 [PATCH] ARM64: Don't set the default console to ttyAMA0 Jon Hunter
2016-02-18 7:15 ` Jisheng Zhang [this message]
2016-02-29 10:46 ` Jon Hunter
2016-02-29 13:20 ` Will Deacon
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=20160218151521.66e0cbf7@xhacker \
--to=jszhang@marvell.com \
--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).