summaryrefslogtreecommitdiff
path: root/rust/zerocopy/src/git@git.tavy.me:linux-stable.git
diff options
context:
space:
mode:
authorJohn Ogness <john.ogness@linutronix.de>2026-07-07 16:16:04 +0206
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2026-07-10 14:47:30 +0200
commit302fbbb4fcbdeac2dc8c63a56c1c4e38c4781958 (patch)
treeb2d33a4f34245cba6c326e6f51e2c051de730382 /rust/zerocopy/src/git@git.tavy.me:linux-stable.git
parentb1b4efea05a56c0995e4702a86d6624b4fdff32f (diff)
serial: 8250: Ignore flow control on suspend/resume with no_console_suspend
If no_console_suspend is specified, on suspend the 8250 console driver uses a scratch register (UART_SCR) to store a special canary value. This is used during the resume path to identify a printk() call before the driver's own ->resume() callback. In this case, serial8250_console_restore() is called to quickly re-init the 8250 for console printing. See commit 4516d50aabed ("serial: 8250: Use canary to restart console after suspend") for the original motivation. Unfortunately, this canary workaround does not work in all cases (such as suspend to mem) because the scratch register will not reset. This has not been a real issue until now because it could simply lead to some garbage characters upon resume. However, with the introduction of console flow control it becomes a real problem because a failed suspend/resume detection when flow control is enabled leads to all characters hitting the flow control timeout. Workaround this issue by temporarily ignoring console flow control when the debug canary suspend/resume detection is active. Fixes: 5e6dfb87b191 ("serial: 8250: Add support for console flow control") Signed-off-by: John Ogness <john.ogness@linutronix.de> Link: https://patch.msgid.link/20260707141032.5074-1-john.ogness@linutronix.de Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'rust/zerocopy/src/git@git.tavy.me:linux-stable.git')
0 files changed, 0 insertions, 0 deletions