Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752141AbdHVSK6 (ORCPT ); Tue, 22 Aug 2017 14:10:58 -0400 Received: from smtprelay4.synopsys.com ([198.182.47.9]:38836 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751716AbdHVSKz (ORCPT ); Tue, 22 Aug 2017 14:10:55 -0400 From: Eugeniy Paltsev To: "linux-serial@vger.kernel.org" CC: "linux-kernel@vger.kernel.org" , "linux-snps-arc@lists.infradead.org" Subject: Specifying console via "stdout-path" property Thread-Topic: Specifying console via "stdout-path" property Thread-Index: AQHTG3H9IpLLL6nIZUWCJgUQHBKhjg== Date: Tue, 22 Aug 2017 18:10:52 +0000 Message-ID: <1503425451.2586.56.camel@synopsys.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.121.8.106] Content-Type: text/plain; charset="utf-8" Content-ID: MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id v7MIB40c008774 Content-Length: 881 Lines: 36 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