public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Sherry Sun <sherry.sun@nxp.com>,
	"esben@geanix.com" <esben@geanix.com>,
	"pmladek@suse.com" <pmladek@suse.com>,
	"senozhatsky@chromium.org" <senozhatsky@chromium.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	Greg KH <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	"ryotkkr98@gmail.com" <ryotkkr98@gmail.com>,
	"kkartik@nvidia.com" <kkartik@nvidia.com>,
	"fj6611ie@aa.jp.fujitsu.com" <fj6611ie@aa.jp.fujitsu.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-serial <linux-serial@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: RE: [BUG] Suspend failure with nbcon + pm_debug_messages (Linux 6.18-rc4)
Date: Tue, 04 Nov 2025 11:22:11 +0106	[thread overview]
Message-ID: <87qzuem7bo.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <DB9PR04MB842977523C92FDE8AF4B714A92C4A@DB9PR04MB8429.eurprd04.prod.outlook.com>

On 2025-11-04, Sherry Sun <sherry.sun@nxp.com> wrote:
>> Thanks for reporting! I believe this is the same issue reported by NVIDIA [0]
>> when we tried to switch the 8250 UART driver to nbcon.
>>
>> We have been working with NVIDIA recently to address the issue. There is a
>> patch [1] we are currently testing that looks good so far. It is based on 6.17
>> but should work fine for 6.18-rc4 as well. Can you give it a spin?
>
> Thanks a lot for your quick reply, I just tried the patch [1] on my
> i.MX8MP EVK with L6.18-rc4, it does fix the suspend issue.  Now i.MX
> UART nbcon can enter suspend with `pm_debug_messages` is turned on.
> May I know what is the upstream plan for the patch [1]?

Thanks for confirming the fix. I will make an official post on LKML with
the patch today. Since the i.MX nbcon-driver is already mainline, I will
CC stable. I will CC you as well.

Note that the patch still needs a formal review from the printk folks
once it hits LKML.

John Ogness

>> [1] https://github.com/Linutronix/linux/commit/ae173249d9028ef159fba040bdab260d80dda43f

  reply	other threads:[~2025-11-04 10:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04  7:44 [BUG] Suspend failure with nbcon + pm_debug_messages (Linux 6.18-rc4) Sherry Sun
2025-11-04  8:28 ` John Ogness
2025-11-04  9:46   ` Sherry Sun
2025-11-04 10:16     ` John Ogness [this message]
2025-11-04 10:43       ` Sherry Sun
2025-11-04 23:19         ` John Ogness
2025-11-05  3:43           ` Sherry Sun
2025-11-05  7:30           ` Petr Mladek

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=87qzuem7bo.fsf@jogness.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=esben@geanix.com \
    --cc=fj6611ie@aa.jp.fujitsu.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=imx@lists.linux.dev \
    --cc=jirislaby@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=kkartik@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=ryotkkr98@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=senozhatsky@chromium.org \
    --cc=shawnguo@kernel.org \
    --cc=sherry.sun@nxp.com \
    --cc=tglx@linutronix.de \
    /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