From nobody Sun May 10 14:18:06 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 51040C433EF for ; Mon, 2 May 2022 09:48:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1384342AbiEBJvs (ORCPT ); Mon, 2 May 2022 05:51:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36788 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1384415AbiEBJvA (ORCPT ); Mon, 2 May 2022 05:51:00 -0400 Received: from alexa-out.qualcomm.com (alexa-out.qualcomm.com [129.46.98.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4C3B113E83; Mon, 2 May 2022 02:47:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1651484851; x=1683020851; h=from:to:cc:subject:date:message-id; bh=lJvh+GysjJsgQmdPaDpyMJYF+wTQQxzW4XnXPVDg9Vw=; b=JgunQ+LjvysXcudWrN8L9OdTMlZwsS1lTDvOUBbNFzqej58ZLyndwRd0 dOyz0pu6EkZFHxEaJkmLhZA3nUuiQUKicP2Tu4YYxpPVd1ipZvVSDkLbV 6bofWbjG01dDAgMTuj2CLUoTphnO7Y/KX/e39AQcUSN8JxdjM+VssDTFz g=; Received: from ironmsg07-lv.qualcomm.com ([10.47.202.151]) by alexa-out.qualcomm.com with ESMTP; 02 May 2022 02:47:30 -0700 X-QCInternal: smtphost Received: from ironmsg02-blr.qualcomm.com ([10.86.208.131]) by ironmsg07-lv.qualcomm.com with ESMTP/TLS/AES256-SHA; 02 May 2022 02:47:29 -0700 X-QCInternal: smtphost Received: from hu-vnivarth-hyd.qualcomm.com (HELO hu-sgudaval-hyd.qualcomm.com) ([10.213.111.166]) by ironmsg02-blr.qualcomm.com with ESMTP; 02 May 2022 15:17:18 +0530 Received: by hu-sgudaval-hyd.qualcomm.com (Postfix, from userid 3994820) id F34363CB4; Mon, 2 May 2022 15:17:17 +0530 (+0530) From: Vijaya Krishna Nivarthi To: gregkh@linuxfoundation.org, jirislaby@kernel.org, linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org Cc: quic_msavaliy@quicinc.com, dianders@chromium.org, Vijaya Krishna Nivarthi Subject: [PATCH] serial: core: Do stop_rx in suspend path for console if console_suspend is disabled Date: Mon, 2 May 2022 15:17:15 +0530 Message-Id: <1651484835-25189-1-git-send-email-quic_vnivarth@quicinc.com> X-Mailer: git-send-email 2.7.4 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" For the case of console_suspend disabled, if back to back suspend/resume test is executed, at the end of test, sometimes console would appear to be frozen not responding to input. This would happen because, during resume, rx transactions can come in before system is ready, malfunction of rx happens in turn resulting in console appearing to be stuck. Do a stop_rx in suspend sequence to prevent this. Signed-off-by: Vijaya Krishna Nivarthi --- drivers/tty/serial/serial_core.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_c= ore.c index 82a1770..e8c6875 100644 --- a/drivers/tty/serial/serial_core.c +++ b/drivers/tty/serial/serial_core.c @@ -2211,9 +2211,16 @@ int uart_suspend_port(struct uart_driver *drv, struc= t uart_port *uport) } put_device(tty_dev); =20 - /* Nothing to do if the console is not suspending */ - if (!console_suspend_enabled && uart_console(uport)) + /* + * Nothing to do if the console is not suspending + * except stop_rx to prevent any asynchronous data + * over RX line. Re start_rx, when required, is + * done by set_termios in resume sequence + */ + if (!console_suspend_enabled && uart_console(uport)) { + uport->ops->stop_rx(uport); goto unlock; + } =20 uport->suspended =3D 1; =20 --=20 Qualcomm INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member o= f the Code Aurora Forum, hosted by the Linux Foundation.