From: Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: Specifying console via "stdout-path" property
Date: Tue, 22 Aug 2017 18:10:52 +0000 [thread overview]
Message-ID: <1503425451.2586.56.camel@synopsys.com> (raw)
Hi everyone,
I got strange results when I tried to specify device to use as console
via "stdout-path" property in device tree:
Even If I specify device in "stdout-path" property first probed device
(of those that can be used as console device) is used as console.
For example:
-------------->8--------
chosen {
????stdout-path = &serial1;
};
serial0: uart0 at ... {} /* serial0 is used as console (ttyS0) as it is
* probed earlier */
serial1: uart1 at ... {}
-------------->8--------
So I am wondering is it expected behavior?
Everything is fine if I specify uart device via "console" parameter in
bootargs:
-------------->8--------
chosen {
????bootargs = "console=ttyS1"
????stdout-path = &serial1;
};
serial0: uart0 at ... {}
serial1: uart1 at ... {} /* serial1 is used as console (ttyS1) */
-------------->8--------
Thanks.
--
?Eugeniy Paltsev
WARNING: multiple messages have this Message-ID (diff)
From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Specifying console via "stdout-path" property
Date: Tue, 22 Aug 2017 18:10:52 +0000 [thread overview]
Message-ID: <1503425451.2586.56.camel@synopsys.com> (raw)
Hi everyone,
I got strange results when I tried to specify device to use as console
via "stdout-path" property in device tree:
Even If I specify device in "stdout-path" property first probed device
(of those that can be used as console device) is used as console.
For example:
-------------->8--------
chosen {
stdout-path = &serial1;
};
serial0: uart0@... {} /* serial0 is used as console (ttyS0) as it is
* probed earlier */
serial1: uart1@... {}
-------------->8--------
So I am wondering is it expected behavior?
Everything is fine if I specify uart device via "console" parameter in
bootargs:
-------------->8--------
chosen {
bootargs = "console=ttyS1"
stdout-path = &serial1;
};
serial0: uart0@... {}
serial1: uart1@... {} /* serial1 is used as console (ttyS1) */
-------------->8--------
Thanks.
--
Eugeniy Paltsev
next reply other threads:[~2017-08-22 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 18:10 Eugeniy Paltsev [this message]
2017-08-22 18:10 ` Specifying console via "stdout-path" property Eugeniy Paltsev
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=1503425451.2586.56.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=linux-snps-arc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.