From: Tony Lindgren <tony@atomide.com>
To: Johan Hovold <johan@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
linux-serial@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Matwey V . Kornilov" <matwey@sai.msu.ru>,
"Steffen Trumtrar" <s.trumtrar@pengutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH 1/2] serial: 8250: Fix runtime PM for start_tx() for RS485
Date: Mon, 11 Apr 2022 13:10:34 +0300 [thread overview]
Message-ID: <YlP+muZF1nDIU0t4@atomide.com> (raw)
In-Reply-To: <YlP7eArvvNWnbMF2@hovoldconsulting.com>
* Johan Hovold <johan@kernel.org> [220411 09:54]:
> On Mon, Apr 11, 2022 at 12:48:04PM +0300, Tony Lindgren wrote:
> > diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c
> > --- a/drivers/tty/serial/8250/8250_port.c
> > +++ b/drivers/tty/serial/8250/8250_port.c
> > @@ -1681,8 +1681,10 @@ static void serial8250_start_tx(struct uart_port *port)
> > return;
> >
> > if (em485 &&
> > - em485->active_timer == &em485->start_tx_timer)
> > + em485->active_timer == &em485->start_tx_timer) {
> > + serial8250_rpm_put_tx(up);
> > return;
> > + }
>
> I was just taking a quick look at your report about this and also
> noticed this return statement.
>
> The runtime PM implementation is a bit of mess as we've discussed
> elsewhere, but the change you propose here doesn't look right.
Frankly "a bit of mess" applies "a bit more" than just the serial runtime
PM :)
> start_tx() can be deferred in the rs485 case, but that doesn't mean you
> should suspend the device here. In fact, that look like it would just
> break runtime PM (the parts that may work to some extent).
AFAIK there's currently nothing paired with the serial8250_rpm_get_tx(up)
call at the beginning of serial8250_start_tx() for the early exit cases
if start_tx_rs485() or __start_tx() won't get called.
Care to clarify a bit more what you have in mind?
Regards,
Tony
next prev parent reply other threads:[~2022-04-11 10:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 9:48 [PATCH 1/2] serial: 8250: Fix runtime PM for start_tx() for RS485 Tony Lindgren
2022-04-11 9:48 ` [PATCH 2/2] serial: 8250: Fix runtime PM for start_tx() for empty buffer Tony Lindgren
2022-04-11 10:02 ` Uwe Kleine-König
2022-04-11 10:12 ` Tony Lindgren
2022-04-11 10:13 ` Johan Hovold
2022-04-11 10:33 ` Tony Lindgren
2022-04-11 9:57 ` [PATCH 1/2] serial: 8250: Fix runtime PM for start_tx() for RS485 Johan Hovold
2022-04-11 10:10 ` Tony Lindgren [this message]
2022-04-11 10:25 ` Johan Hovold
2022-04-11 10:32 ` Tony Lindgren
2022-04-11 11:56 ` Johan Hovold
2022-04-11 12:01 ` Tony Lindgren
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=YlP+muZF1nDIU0t4@atomide.com \
--to=tony@atomide.com \
--cc=andriy.shevchenko@intel.com \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=matwey@sai.msu.ru \
--cc=s.trumtrar@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).