From: Alex Henrie <alexh@vpitech.com>
To: Johan Hovold <johan@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
linux-usb@vger.kernel.org, alexhenrie24@gmail.com,
Sergey Shtylyov <s.shtylyov@omp.ru>
Subject: Re: [PATCH] USB: serial: cp210x: map B0 to B9600
Date: Tue, 29 Nov 2022 10:48:02 -0700 [thread overview]
Message-ID: <4443793.LvFx2qVVIh@demeter> (raw)
In-Reply-To: <Y4YT7D6AoD31UdOC@hovoldconsulting.com>
On Tuesday, November 29, 2022 7:15:08 AM MST Johan Hovold wrote:
> Also note that the FTDI driver does in fact leave the line speed
> unchanged when B0 is requested (that zero-baud check in
> get_ftdi_divisor() is only used for ASYNC_SPD_CUST).
I tested it empirically today, and you're right, the FTDI driver simply does
not change the baud rate. Thank you for correcting my misunderstanding.
> Your application really should not depend on any particular hardware
> setting after requesting B0.
Understood.
> That said, I've implemented support for B0 in cp210x which leaves the
> current settings unchanged (and which incidentally allows you to
> use the buggy tool).
Excellent! Many thanks!
-Alex
next prev parent reply other threads:[~2022-11-29 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 3:58 [PATCH] USB: serial: cp210x: map B0 to B9600 Alex Henrie
2022-11-26 7:10 ` Greg KH
2022-11-28 18:06 ` Alex Henrie
2022-11-26 10:34 ` Sergey Shtylyov
2022-11-28 14:41 ` Johan Hovold
2022-11-28 18:08 ` Alex Henrie
2022-11-28 18:20 ` Russell King (Oracle)
2022-11-28 18:38 ` Alex Henrie
2022-11-29 14:15 ` Johan Hovold
2022-11-29 17:48 ` Alex Henrie [this message]
2022-11-28 18:12 ` [PATCH v2] " Alex Henrie
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=4443793.LvFx2qVVIh@demeter \
--to=alexh@vpitech.com \
--cc=alexhenrie24@gmail.com \
--cc=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=s.shtylyov@omp.ru \
/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