[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230927074104.GD5285@atomide.com>
Date: Wed, 27 Sep 2023 10:41:04 +0300
From: Tony Lindgren <tony@...mide.com>
To: Andy Shevchenko <andriy.shevchenko@...el.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>, Dhruva Gole <d-gole@...com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
John Ogness <john.ogness@...utronix.de>,
Johan Hovold <johan@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Vignesh Raghavendra <vigneshr@...com>,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
Udit Kumar <u-kumar1@...com>,
Thomas Richard <thomas.richard@...tlin.com>
Subject: Re: [PATCH] serial: 8250_omap: Fix errors with no_console_suspend
* Tony Lindgren <tony@...mide.com> [230927 07:29]:
> * Andy Shevchenko <andriy.shevchenko@...el.com> [230926 11:59]:
> > Btw, how close are we to getting rid the pm_runtime_irq_safe() call?
>
> Very close, I think still doable for v6.7 merge window.. Below is what I'm
> testing with, there's one error that I've seen that may or may not be
> related.
I'm unable to reproduce the issue I was seeing with v6.6-rc3 with and without
the pm_runtime_irq_safe() dropping patch. So AFAIK no issues dropping
pm_runtime_irq_safe().
I was seeing some warning earlier after detaching kernel console and doing
any sysrq trigger on the serial port, seems like it was unrelated.
Regards,
Tony
Powered by blists - more mailing lists