From: Greg KH <gregkh@linuxfoundation.org>
To: Yicong Yang <yangyicong@huawei.com>
Cc: jirislaby@kernel.org, tony@atomide.com,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
john.ogness@linutronix.de, andriy.shevchenko@linux.intel.com,
tglx@linutronix.de, yangyicong@hisilicon.com,
linuxarm@huawei.com, prime.zeng@hisilicon.com,
jonathan.cameron@huawei.com, fanghao11@huawei.com
Subject: Re: [PATCH v2] serial: port: Don't suspend if the port is still busy
Date: Tue, 6 Feb 2024 09:44:30 +0000 [thread overview]
Message-ID: <2024020600-attendant-verbally-6441@gregkh> (raw)
In-Reply-To: <20240206073322.5560-1-yangyicong@huawei.com>
On Tue, Feb 06, 2024 at 03:33:22PM +0800, Yicong Yang wrote:
> From: Yicong Yang <yangyicong@hisilicon.com>
>
> We accidently met the issue that the bash prompt is not shown after the
> previous command done and until the next input if there's only one CPU
> (In our issue other CPUs are isolated by isolcpus=). Further analysis
> shows it's because the port entering runtime suspend even if there's
> still pending chars in the buffer and the pending chars will only be
> processed in next device resuming. We are using amba-pl011 and the
> problematic flow is like below:
>
> Bash kworker
> tty_write()
> file_tty_write()
> n_tty_write()
> uart_write()
> __uart_start()
> pm_runtime_get() // wakeup waker
> queue_work()
> pm_runtime_work()
> rpm_resume()
> status = RPM_RESUMING
> serial_port_runtime_resume()
> port->ops->start_tx()
> pl011_tx_chars()
> uart_write_wakeup()
> […]
> __uart_start()
> pm_runtime_get() < 0 // because runtime status = RPM_RESUMING
> // later data are not commit to the port driver
> status = RPM_ACTIVE
> rpm_idle() -> rpm_suspend()
>
> This patch tries to fix this by checking the port busy before entering
> runtime suspending. A runtime_suspend callback is added for the port
> driver. When entering runtime suspend the callback is invoked, if there's
> still pending chars in the buffer then flush the buffer.
>
> Cc: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
Is this a regression that was caused by the port code? If so, what
commit id does this fix? Should it be backported to older kernels?
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-06 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 7:33 [PATCH v2] serial: port: Don't suspend if the port is still busy Yicong Yang
2024-02-06 8:34 ` Tony Lindgren
2024-02-06 9:44 ` Greg KH [this message]
2024-02-06 10:20 ` Yicong Yang
2024-02-06 13:09 ` Andy Shevchenko
2024-02-06 13:11 ` Andy Shevchenko
2024-02-06 13:21 ` Tony Lindgren
2024-02-07 7:22 ` Yicong Yang
2024-02-07 14:47 ` Andy Shevchenko
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=2024020600-attendant-verbally-6441@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fanghao11@huawei.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@huawei.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