From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Lukasz Majczak <lma@semihalf.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Guenter Roeck <groeck@chromium.org>,
linux-serial <linux-serial@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
upstream@semihalf.com, stable@vger.kernel.org
Subject: Re: [PATCH] serial: core: fix broken console after suspend
Date: Wed, 1 Mar 2023 13:33:09 +0200 (EET) [thread overview]
Message-ID: <1ffc536e-9bdc-c246-d31d-ae368fcf6072@linux.intel.com> (raw)
In-Reply-To: <20230301075751.43839-1-lma@semihalf.com>
On Wed, 1 Mar 2023, Lukasz Majczak wrote:
> Re-enable the console device after suspending, causes its cflags,
Re-enabling
> ispeed and ospeed to be set anew, basing on the values stored in
> uport->cons. The issue is that these values are set only once,
> when parsing console parameters after boot (see uart_set_options()),
Remove "The issue is that" from here and just state:
"These values are set only once when parsing console parameters after boot
(see uart_set_options())."
> next after configuring a port in uart_port_startup() these parameteres
parameters
> (cflags, ispeed and ospeed) are copied to termios structure and
> the orginal one (stored in uport->cons) are cleared, but there is no place
original
> in code where those fields are checked against 0.
> When kernel calls uart_resume_port() and setups console, it copies cflags,
> ispeed and ospeed values from uart->cons,but those are alread cleared.
missing space after comma.
alread -> already
> The efect is that console is broken.
effect
> This patch address this by preserving the cflags, ispeed and
Too many "this", don't start with "This patch" but go directly to the
point.
--
i.
> ospeed fields in uart->cons during uart_port_startup().
>
> Signed-off-by: Lukasz Majczak <lma@semihalf.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/tty/serial/serial_core.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
> index 2bd32c8ece39..394a05c09d87 100644
> --- a/drivers/tty/serial/serial_core.c
> +++ b/drivers/tty/serial/serial_core.c
> @@ -225,9 +225,6 @@ static int uart_port_startup(struct tty_struct *tty, struct uart_state *state,
> tty->termios.c_cflag = uport->cons->cflag;
> tty->termios.c_ispeed = uport->cons->ispeed;
> tty->termios.c_ospeed = uport->cons->ospeed;
> - uport->cons->cflag = 0;
> - uport->cons->ispeed = 0;
> - uport->cons->ospeed = 0;
> }
> /*
> * Initialise the hardware port settings.
>
prev parent reply other threads:[~2023-03-01 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 7:57 [PATCH] serial: core: fix broken console after suspend Lukasz Majczak
2023-03-01 8:39 ` Greg Kroah-Hartman
2023-03-01 9:51 ` Lukasz Majczak
2023-03-01 12:22 ` Greg Kroah-Hartman
2023-03-01 14:09 ` Lukasz Majczak
2023-03-02 16:43 ` Lukasz Majczak
2023-03-01 11:33 ` Ilpo Järvinen [this message]
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=1ffc536e-9bdc-c246-d31d-ae368fcf6072@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lma@semihalf.com \
--cc=stable@vger.kernel.org \
--cc=upstream@semihalf.com \
/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 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).