Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp4930456imm; Tue, 19 Jun 2018 02:09:04 -0700 (PDT) X-Google-Smtp-Source: ADUXVKInFSwn2tcOUc8B0VtS6EVYVRXA5rrf1ry87HHTILdOWbLmMcjPv84eYh7Jv1mgAPNOPWrk X-Received: by 2002:a17:902:a9:: with SMTP id a38-v6mr18215512pla.102.1529399344733; Tue, 19 Jun 2018 02:09:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529399344; cv=none; d=google.com; s=arc-20160816; b=aFBVjZQVKmrY3gOkFRfdPkwRSR5ynN4q091o70eRuun+uUsjeXyOKLnlnNNEfyR9wY ToBZlHG3uNYShr/kCgdAAadPML4/h5D3J0R1uCxiuqquu1laAr6hV6iY0IIHwIVVqG6/ kveq0fbJdIatRR3NnO0ZxE8suQCqQK1csrIQ/vCVR3JS6u3bmvQCBNtWBL7B+HiJswri mH+bLOvmOkI4HlHTJkmPZgZrxuhvKzrw9zk05QCHGbsNPJCmDI3fHYt0NyLrpi52LDO5 hxwNzAytJf1WHVqBDaf2nhhDnE1SYGSt3l2avamAaHaDVxjiBeidL0I536uX6tzx71XA 46jQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=ZCCO3WV09NH9NjFd2a1qrac2x+2xzEouHqSewxdWkjQ=; b=n/q49dM92CUS7v/pcqX6luLSxVAUHEk+6YUPhTWb5wO1Ztq4wmuMOEofL9+GKbujps SfEBeHlqm059vCCb3sjpV8EMRJ1gnBNybrxC1ulMK3pIw8IqU4o+ogK8UwzUdg9mA8yi 9+OdbjzcjV4y2bUb1ovgHCCRA3C9Z9O2F/0oxNNOfCsBjEAJLLZv30LZHXlLqj64M3MX 1tgfB92yhgVhyGM7oxisUpsoj+T8vSXZWr23nii1Gtse6CfzUAoDEhIhxmCdrScSwUQM AclzluZQghE8/jeFG2hNvpZkGU5PNcDBFsAw5vaF9g9UjVVOgRscowV4qFlStye1bPD4 FNuw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m5-v6si2592005plt.468.2018.06.19.02.08.51; Tue, 19 Jun 2018 02:09:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756590AbeFSJHO (ORCPT + 99 others); Tue, 19 Jun 2018 05:07:14 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:45546 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756178AbeFSJHL (ORCPT ); Tue, 19 Jun 2018 05:07:11 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 089661435; Tue, 19 Jun 2018 02:07:11 -0700 (PDT) Received: from [10.1.78.251] (unknown [10.1.78.251]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 719A63F25D; Tue, 19 Jun 2018 02:07:09 -0700 (PDT) Subject: Re: [PATCH] serial: mps2-uart: Initialize early console To: Guenter Roeck , Greg Kroah-Hartman Cc: Jiri Slaby , linux-serial@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Liviu Dudau , Sudeep Holla , Lorenzo Pieralisi References: <1529384097-1631-1-git-send-email-linux@roeck-us.net> From: Vladimir Murzin Message-ID: <173551dd-3632-08a6-ec42-2ee416ccb9ad@arm.com> Date: Tue, 19 Jun 2018 10:07:01 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1529384097-1631-1-git-send-email-linux@roeck-us.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Guenter, On 19/06/18 05:54, Guenter Roeck wrote: > The early console code for mps2-uart assumes that the serial hardware is > enabled for transmit when the system boots. However, this is not the case > after reset. This results in a hang in mps2_early_putchar() if the serial > transmitter is not enabled by a boot loader or ROM monitor. I was under impression that for earlycon there is an assumption/requirement that the serial port must already be setup and configured. For instance, I see such requirement for pl011. So it looks like boot code's fault not to enable serial (for mps2 it needs to setup BAUDDIV as well). I'm not against the patch per se, but I'd like to hear if my understanding of earlycon requirements is correct or not. Cheers Vladimir > > Signed-off-by: Guenter Roeck > --- > drivers/tty/serial/mps2-uart.c | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/drivers/tty/serial/mps2-uart.c b/drivers/tty/serial/mps2-uart.c > index 9f8f63719126..0743a0551ce1 100644 > --- a/drivers/tty/serial/mps2-uart.c > +++ b/drivers/tty/serial/mps2-uart.c > @@ -448,6 +448,14 @@ static struct console mps2_uart_console = { > > #define MPS2_SERIAL_CONSOLE (&mps2_uart_console) > > +static void mps2_early_init(struct uart_port *port) > +{ > + u8 control = readb(port->membase + UARTn_CTRL); > + > + control |= UARTn_CTRL_TX_ENABLE; > + writeb(control, port->membase + UARTn_CTRL); > +} > + > static void mps2_early_putchar(struct uart_port *port, int ch) > { > while (readb(port->membase + UARTn_STATE) & UARTn_STATE_TX_FULL) > @@ -469,6 +477,7 @@ static int __init mps2_early_console_setup(struct earlycon_device *device, > if (!device->port.membase) > return -ENODEV; > > + mps2_early_init(&device->port); > device->con->write = mps2_early_write; > > return 0; >