From: Johan Hovold <johan@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Marek Behún" <kabel@kernel.org>,
linux-usb@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 6/7] USB: serial: ftdi_sio: Fix custom_divisor and c_*speed for ASYNC_SPD_CUST
Date: Sun, 24 Jul 2022 14:54:58 +0200 [thread overview]
Message-ID: <Yt1BIsPqAVH0ajlf@hovoldconsulting.com> (raw)
In-Reply-To: <20220724123351.icqqvvfxjm7ogo5u@pali>
On Sun, Jul 24, 2022 at 02:33:51PM +0200, Pali Rohár wrote:
> On Sunday 24 July 2022 14:28:43 Johan Hovold wrote:
> > On Tue, Jul 12, 2022 at 01:53:05PM +0200, Marek Behún wrote:
> > > From: Pali Rohár <pali@kernel.org>
> > >
> > > When ASYNC_SPD_CUST is used, update custom_divisor and c_*speed fields
> > > so that they correspond to the newly set baud rate value, so that
> > > userspace GET ioctls will see the true baud rate that is being used.
> >
> > No, this is wrong.
> >
> > In fact, there's a long-standing bug in this driver which started
> > reporting back the actual baud rate when using SPD_CUST.
>
> Hello! And this commit is fixing also this bug as a side change.
Ah, indeed it is, or at least to some extent.
> > The rate should be left unchanged at 38400 in that case.
>
> With this change, rate in c_cflag is unchanged and stays at B38400.
Right.
> What is updated is the real baudrate in c_ispeed and c_ospeed
> extensions.
>
> It is really wrong? I thought that c_cflag should stay unchanged at
> B38400 when ASYNC_SPD_CUST is used.
Yeah, cflags stay unchanged, but you shouldn't touch those fields when
using the deprecated ASYNC_SPD_CUST hack.
Note that this currently only works because the ftdi driver uses
tty_get_baud_rate() instead of c_ospeed directly which is the
recommended (new) way.
> > > + /* Fix deprecated async-compatible custom_divisor hack and update tty baud rate */
> > > + if (fix_custom_divisor) {
> > > + priv->custom_divisor = DIV_ROUND_CLOSEST(priv->baud_base, baud);
> > > + old_baud = baud;
> > > + baud = 38400;
> > > + }
> > > +
> > > tty_encode_baud_rate(tty, baud, baud);
> > > +
> > > + /* For async-compatible custom_divisor store into TCGETS2 c_*speed fields real baud rate */
> > > + if (fix_custom_divisor)
> > > + tty->termios.c_ispeed = tty->termios.c_ospeed = old_baud;
> > > +
> > > return div_value;
> > > }
> > >
> > > @@ -2674,6 +2688,8 @@ static void ftdi_set_termios(struct tty_struct *tty,
> > > dev_dbg(ddev, "%s: forcing baud rate for this device\n", __func__);
> > > tty_encode_baud_rate(tty, priv->force_baud,
> > > priv->force_baud);
> > > + termios->c_ispeed = termios->c_ospeed =
> > > + DIV_ROUND_CLOSEST(priv->baud_base, priv->custom_divisor);
> > > }
> > >
> > > /* Force RTS-CTS if this device requires it. */
Johan
next prev parent reply other threads:[~2022-07-24 12:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 11:52 [PATCH v2 0/7] ftdi_sio driver improvements Marek Behún
2022-07-12 11:53 ` [PATCH v2 1/7] USB: serial: ftdi_sio: Fix divisor overflow Marek Behún
2022-07-24 12:02 ` Johan Hovold
2022-07-12 11:53 ` [PATCH v2 2/7] USB: serial: ftdi_sio: Add missing baud rate validation Marek Behún
2022-07-12 17:27 ` Rob Pearce
2022-07-12 22:24 ` Marek Behún
2022-07-12 11:53 ` [PATCH v2 3/7] USB: serial: ftdi_sio: Extract SIO divisor code to function Marek Behún
2022-07-24 12:06 ` Johan Hovold
2022-08-18 14:11 ` Pali Rohár
2022-09-13 14:49 ` Johan Hovold
2022-09-13 15:30 ` Pali Rohár
2022-09-13 15:44 ` Johan Hovold
2022-07-12 11:53 ` [PATCH v2 4/7] USB: serial: ftdi_sio: Do not reset baud rate to 9600 Baud on error Marek Behún
2022-07-24 12:20 ` Johan Hovold
2022-08-18 14:12 ` Pali Rohár
2022-09-13 14:54 ` Johan Hovold
2022-07-12 11:53 ` [PATCH v2 5/7] USB: serial: ftdi_sio: Fix baud rate rounding for ASYNC_SPD_CUST Marek Behún
2022-07-24 12:26 ` Johan Hovold
2022-07-12 11:53 ` [PATCH v2 6/7] USB: serial: ftdi_sio: Fix custom_divisor and c_*speed " Marek Behún
2022-07-24 12:28 ` Johan Hovold
2022-07-24 12:33 ` Pali Rohár
2022-07-24 12:54 ` Johan Hovold [this message]
2022-07-24 12:59 ` Pali Rohár
2022-07-24 13:08 ` Johan Hovold
2022-08-18 14:09 ` Pali Rohár
2022-09-13 14:59 ` Johan Hovold
2022-09-14 8:48 ` Pali Rohár
2022-09-14 8:58 ` Johan Hovold
2022-09-14 9:10 ` Pali Rohár
2022-09-14 9:18 ` Johan Hovold
2022-09-14 9:20 ` Pali Rohár
2022-07-12 11:53 ` [PATCH v2 7/7] USB: serial: ftdi_sio: Fill c_*speed fields with real baud rate Marek Behún
2022-07-24 12:41 ` Johan Hovold
2022-08-18 14:17 ` Pali Rohár
2022-09-13 15:02 ` Johan Hovold
2022-09-13 15:24 ` Pali Rohár
2022-09-13 15:34 ` Johan Hovold
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=Yt1BIsPqAVH0ajlf@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kabel@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pali@kernel.org \
/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).