* Specifying console via "stdout-path" property
@ 2017-08-22 18:10 Eugeniy Paltsev
0 siblings, 0 replies; only message in thread
From: Eugeniy Paltsev @ 2017-08-22 18:10 UTC (permalink / raw)
To: linux-serial@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-snps-arc@lists.infradead.org
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-08-22 18:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-22 18:10 Specifying console via "stdout-path" property Eugeniy Paltsev
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).