From: Lukasz Majczak <lma@semihalf.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
upstream@semihalf.com, Lukasz Majczak <lma@semihalf.com>
Subject: [PATCH v2 0/2] serial: core: fix broken console after suspend
Date: Wed, 5 Apr 2023 13:15:57 +0200 [thread overview]
Message-ID: <20230405111559.110220-1-lma@semihalf.com> (raw)
This is v2 of a patch[1].
v1->v2:
* Fixed typos in commit message
* Tested[2] patch "serial: core: preserve cflags, ispeed and ospeed" on all
current LTS kernels (4.14, 4.19, 5.4, 5.10, 5.15, 6.1) and on top of
6.3-rc5 with positive results - console was working after resume
* During tests another issue was observed on 6.1+ - FIFO not enabled after
resume - and an additional change was needed ("serial: core: enable
FIFO after resume")
* Test procedure:
1) ensure the console output is ok
2) suspend device with "echo freeze > /sys/power/state"
(/sys/module/printk/parameters/console_suspend == N)
3) resume device and check the console output
4) suspend device with "echo freeze > /sys/power/state"
(/sys/module/printk/parameters/console_suspend == Y)
5) resume device and check the console output
[1] https://lore.kernel.org/lkml/20230301075751.43839-1-lma@semihalf.com/
[2] Test platforms: PC with i5-8400 + GB H370M D3H
HP Elite c1030 Chromebook Enterprise i5-10310U
Lukasz Majczak (2):
serial: core: preserve cflags, ispeed and ospeed
serial: core: enable FIFO after resume
drivers/tty/serial/serial_core.c | 57 +++++++++++++++-----------------
1 file changed, 27 insertions(+), 30 deletions(-)
--
2.40.0.577.gac1e443424-goog
next reply other threads:[~2023-04-05 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 11:15 Lukasz Majczak [this message]
2023-04-05 11:15 ` [PATCH v2 1/2] serial: core: preserve cflags, ispeed and ospeed Lukasz Majczak
2023-04-05 11:15 ` [PATCH v2 2/2] serial: core: enable FIFO after resume Lukasz Majczak
2023-05-10 11:43 ` Ilpo Järvinen
2023-05-10 6:10 ` [PATCH v2 0/2] serial: core: fix broken console after suspend Lukasz Majczak
2023-05-10 6:35 ` Greg Kroah-Hartman
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=20230405111559.110220-1-lma@semihalf.com \
--to=lma@semihalf.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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
all inboxes | Powered by JetHome®