From: Tony Lindgren <tony@atomide.com>
To: Yicong Yang <yangyicong@huawei.com>
Cc: yangyicong@hisilicon.com, gregkh@linuxfoundation.org,
jirislaby@kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, john.ogness@linutronix.de,
andriy.shevchenko@linux.intel.com, tglx@linutronix.de,
linuxarm@huawei.com, prime.zeng@hisilicon.com,
jonathan.cameron@huawei.com, fanghao11@huawei.com
Subject: Re: [PATCH] serial: port: Don't suspend if the port is still busy
Date: Mon, 5 Feb 2024 11:07:13 +0200 [thread overview]
Message-ID: <20240205090713.GE5185@atomide.com> (raw)
In-Reply-To: <b1518b0f-977a-58f5-3164-a6bb9a45dfbe@huawei.com>
* Yicong Yang <yangyicong@huawei.com> [240205 08:55]:
> On 2024/2/5 14:51, Tony Lindgren wrote:
> > Can you please confirm if this still happens also with commit 6f699743aebf
> > ("serial: core: Fix runtime PM handling for pending tx")? It adds a check
> > for -EINPROGRESS.
>
> Tested nagetive on latest v6.8-rc3. Paste the current code snippet below in __uart_start():
OK thanks for confirming it.
> In our issue case, the dev->power.runtime_status == RPM_RESUMING as analyzed in
> commit. So we cannot pass the pm_runtime_active() check and the chars will still
> be pending.
OK
> Do you mean something like below?
>
> static int serial_port_runtime_suspend(struct device *dev)
> {
> struct serial_port_device *port_dev = to_serial_base_port_device(dev);
> struct uart_port *port;
> unsigned long flags;
> int ret = 0;
>
> port = port_dev->port;
>
> if (port->flags & UPF_DEAD)
> return ret;
>
> spin_lock_irqsave(&port->lock, flags);
> if (__serial_port_busy(port)) {
> port->ops->start_tx(port);
> ret = -EBUSY;
> }
> spin_unlock_irqrestore(&port->lock, flags);
>
> return ret;
> }
Yes the above should work.
> If so will the port fail to suspend after flushing the pending chars? Considering
> underlay driver like amba-pl011 doesn't implement runtime power management, does
> anyone will get the port into suspend routine later? I'm not quite sure about it.
Hmm yeah you may need to also call pm_runtime_mark_last_busy() to
ensure the port gets idled later on. Not sure if PM runtime core does that for
you on returning -EBUSY, worth checking it :)
The PM runtime hierarchy will block the serial port controller driver from
suspending, so the port drivers won't runtime suspend.
> In the patch's implementation the pending chars will be flushed in runtime_resume()
> callback and rpm_resume() will try to call rpm_idle() later.
On serial_port_runtime_suspend() the serial port controller will be active, so
you can call start_tx() directly.
Regards,
Tony
next prev parent reply other threads:[~2024-02-05 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 3:19 [PATCH] serial: port: Don't suspend if the port is still busy Yicong Yang
2024-02-05 6:51 ` Tony Lindgren
2024-02-05 8:55 ` Yicong Yang
2024-02-05 9:07 ` Tony Lindgren [this message]
2024-02-06 8:02 ` Yicong Yang
2024-02-05 8:47 ` John Ogness
2024-02-05 9:00 ` Yicong Yang
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=20240205090713.GE5185@atomide.com \
--to=tony@atomide.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fanghao11@huawei.com \
--cc=gregkh@linuxfoundation.org \
--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=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