Linux Serial subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Birk Skyum" <birk.skyum@pm.me>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] serial: qcom-geni: Set the serial engine up again after hibernation
Date: Tue, 27 Oct 2026 23:01:48 +0000	[thread overview]
Message-ID: <sashiko-outbox-187185@kernel.org> (raw)
In-Reply-To: <20261027224800.86418-1-birk.skyum@pm.me>

> A hibernation image is restored after a power cycle, which resets every
> serial engine. The kernel that loads the image only sets up the engines
> it uses itself, and on laptops the Bluetooth UART is opened from the
> root file system, so that kernel never touches it.
> 
> The restored kernel still has port->setup set from before, so the
> startup in uart_resume_port() skips qcom_geni_serial_port_setup() and
> the port runs on an engine whose FIFOs, packing and transfer mode were
> never configured. On a Lenovo Yoga Slim 7x (X1E80100) the WCN7850's
> Bluetooth controller then never comes back: every setup attempt of
> hci_qca's error recovery ends in "command 0xfc00 tx timeout" and
> "Reading QCA version information failed (-110)".
> 
> Clear port->setup in a restore callback of its own, so the next startup
> sets the engine up again. Leave console ports alone: the kernel that
> loads the image sets up its console when it registers it, and setting
> the engine up again in qcom_geni_serial_startup() would run without the
> port lock while the console may be writing. The other system sleep
> callbacks are unchanged.
> 
> Signed-off-by: Birk Skyum <birk.skyum@pm.me>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261027224800.86418-1-birk.skyum@pm.me?part=1


      reply	other threads:[~2026-10-27 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 22:48 [PATCH v2] serial: qcom-geni: Set the serial engine up again after hibernation Birk Skyum
2026-10-27 23:01 ` sashiko-bot [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=sashiko-outbox-187185@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=birk.skyum@pm.me \
    --cc=linux-serial@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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