From: David Heidelberg <david@ixit.cz>
To: Konrad Dybcio <konradybcio@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Praveen Talari <praveen.talari@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH] serial: qcom-geni: keep registered console runtime active
Date: Fri, 18 Sep 2026 00:10:00 +0200 [thread overview]
Message-ID: <34d95e25-be4a-406c-b486-0ad9e7c86838@ixit.cz> (raw)
In-Reply-To: <20260819-topic-geni_console_poweredoff-v1-1-7f7bb3aad8da@oss.qualcomm.com>
On 19/08/2026 18:46, Konrad Dybcio wrote:
> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>
> Commit aee1f94dab13 ("serial: qcom-geni: remove .pm callback, use
> runtime PM in startup/shutdown") moved runtime PM references from the
> serial-core PM callback to the port startup and shutdown callbacks.
>
> The serial core used to leave the console port powered after
> registration, but after the callback was removed the temporary probe
> reference is always released. Console writes are not tied to an open TTY
> and can run from contexts which cannot resume the device, so a
> runtime-suspended console can stall. This was observed on a Qualcomm
> X1E80100 CRD device, as the boot console became flakey across boots.
>
> Acquire a runtime PM reference when the console is set up and release it
> through the console exit callback. This keeps the device active only
> while the console is registered and balances the reference when the
> console is disabled or re-enabled through sysfs.
>
> Fixes: aee1f94dab13 ("serial: qcom-geni: remove .pm callback, use runtime PM in startup/shutdown")
> Assisted-by: LLM
> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> ---
> drivers/tty/serial/qcom_geni_serial.c | 26 ++++++++++++++++++++++++--
> 1 file changed, 24 insertions(+), 2 deletions(-)
>
This also fixes a regression on sdm845: since v7.3-rc1 (or on next-20260820),
OnePlus 6 and 6T crash into the Qualcomm crash dump mode on every s2idle suspend
attempt (no kernel output, warm reset via PS_HOLD with the TZ download cookie
set, no panic in ramoops).
Tested-by: David Heidelberg <david@ixit.cz> # OnePlus 6T (sdm845)
One thing this leaves open: with the console holding a single reference,
pm_runtime_force_suspend() goes through pm_runtime_need_not_resume() and
pm_runtime_force_resume() does not power the port back up, so
uart_resume_port() programs the termios and resumes the console on a
powered-down port; it only comes back through startup() if the tty was
open. I'll send a patch on top for that.
Thank you
David
prev parent reply other threads:[~2026-09-17 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 16:46 Konrad Dybcio
2026-08-19 17:13 ` Abel Vesa
2026-09-17 22:10 ` David Heidelberg [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=34d95e25-be4a-406c-b486-0ad9e7c86838@ixit.cz \
--to=david@ixit.cz \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=praveen.talari@oss.qualcomm.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®