Linux Serial subsystem development
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Tomasz Mon <tomasz.mon@camlingroup.com>
Cc: "nunojpg@gmail.com" <nunojpg@gmail.com>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: [RFC PATCH] serial: Don't assume uart_ops .throttle is always set
Date: Fri, 29 Apr 2022 10:19:33 +0300 (EEST)	[thread overview]
Message-ID: <717acce-e7c-559-863d-947b15fe4170@linux.intel.com> (raw)
In-Reply-To: <d16634147375cbebad48b143974432e0f40f842d.camel@camlingroup.com>

[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]

On Fri, 29 Apr 2022, Tomasz Mon wrote:

> On Thu, 2022-04-28 at 20:11 +0300, Ilpo Järvinen wrote:
> > uart_throttle() assumes that a driver provides a throttle function in
> > uart_ops. But not all drivers do and there seems to nothing in
> > serial_core that would set it either. Thus, check it before calling.
> 
> If the driver does not provide throttle function, it should not
> set UPSTAT_AUTORTS nor UPSTAT_AUTOXOFF in port->status.
> 
> > diff --git a/drivers/tty/serial/serial_core.c
> > b/drivers/tty/serial/serial_core.c
> > index 6a8963caf954..18c9d46e0b85 100644
> > --- a/drivers/tty/serial/serial_core.c
> > +++ b/drivers/tty/serial/serial_core.c
> > @@ -697,7 +697,8 @@ static void uart_throttle(struct tty_struct *tty)
> >  		mask |= UPSTAT_AUTORTS;
> >  
> >  	if (port->status & mask) {
> 
> This if condition is always false if driver did not set UPSTAT_AUTORTS
> nor UPSTAT_AUTOXOFF in port->status.
> 
> > -		port->ops->throttle(port);
> > +		if (port->ops->throttle)
> > +			port->ops->throttle(port);
> >  		mask &= ~port->status;
> >  	}
> > 
> 
> I think this patch is incorrect. The assumption is not ".throttle is
> always set" but rather ".throttle is set when UPSTAT_AUTORTS or
> UPSTAT_AUTOXOFF is set".

Right, I kind of ended up concluding that's likely the case after sending 
the patch when looking into 9aba8d5b0111 (SERIAL: core: add 
throttle/unthrottle callbacks for hardware assisted flow control).


-- 
 i.

      reply	other threads:[~2022-04-29  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 17:11 [RFC PATCH] serial: Don't assume uart_ops .throttle is always set Ilpo Järvinen
2022-04-28 18:37 ` Greg KH
2022-04-29  5:21 ` Tomasz Mon
2022-04-29  7:19   ` Ilpo Järvinen [this message]

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=717acce-e7c-559-863d-947b15fe4170@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=nunojpg@gmail.com \
    --cc=tomasz.mon@camlingroup.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