From: Johan Hovold <johan@kernel.org>
To: "Michael G. Katzmann" <michaelk@IEEE.org>
Cc: "Charles Yeh" <charlesyeh522@gmail.com>,
"Yeh.Charles [葉榮鑫]" <charles-yeh@prolific.com.tw>,
linux-serial@vger.kernel.org, linux-usb@vger.kernel.org,
"Joe Abbott" <jabbott@rollanet.org>
Subject: Re: non-standard baud rates with Prolific 2303 USB-serial
Date: Fri, 12 Mar 2021 14:44:23 +0100 [thread overview]
Message-ID: <YEtwNzhCmvyKhRto@hovoldconsulting.com> (raw)
In-Reply-To: <9d02257d-cca1-116e-634a-6ac952362c5d@IEEE.org>
On Fri, Mar 12, 2021 at 08:17:55AM -0500, Michael G. Katzmann wrote:
> On 3/11/21 11:08 AM, Johan Hovold wrote:
> >> static speed_t pl2303_encode_baud_rate_divisor( struct usb_serial_port *port,
> >> unsigned char buf[4],
> >> speed_t baud)
> >> {
> >> unsigned int baseline, mantissa, exponent;
> >> struct usb_serial *serial = port->serial;
> >> struct pl2303_serial_private *spriv = usb_get_serial_data(serial);
> >>
> >> /*
> >> * Apparently the formula is:
> >> * baudrate = 12M * 32 / (mantissa * 4^exponent)
> >> * where
> >> * mantissa = buf[8:0]
> >> * exponent = buf[11:9]
> >> *
> >> * TA version has more precision
> >> * uses mantissa = buf[bits 10:0 ]
> > So you discovered that there were even more bits here? Your first
> > version used ten bits, I believe.
> >
> > I got an offline mail from a third person having problems with the TA
> > and who had also verified eleven bits here.
>
> I was basing this on Joe's discovery of the value used for 110 bd by
> the windows driver (confirmed by Charles). The sequence 80 01 a6 a8
> implies that the mantissa is 0x6a8 (i.e. 11 bits). The tests that I
> did seemed to confirm this.
Ah, of course.
> Pardon my ignorance of the process but where is the git repo for this
> development branch?
I'll wait for a few days before applying the series I posted yesterday
to the usb-next (development) branch, but I've pushed a pl2303-wip
branch for you that you can use use until then:
https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git/log/?h=pl2303-wip
You can fetch from
https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git
Johan
next prev parent reply other threads:[~2021-03-12 13:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3aee5708-7961-f464-8c5f-6685d96920d6@IEEE.org>
[not found] ` <dc3458f1-830b-284b-3464-20124dc3900a@IEEE.org>
2021-02-22 8:52 ` non-standard baud rates with Prolific 2303 USB-serial Johan Hovold
2021-02-22 12:39 ` Michael G. Katzmann
2021-02-22 13:18 ` Johan Hovold
[not found] ` <fb1489c2-b972-619b-b7ce-4ae8e1d2cc0f@IEEE.org>
2021-02-22 15:34 ` Johan Hovold
2021-02-22 15:42 ` Michael G. Katzmann
2021-02-22 15:50 ` Johan Hovold
2021-02-22 16:37 ` Michael G. Katzmann
2021-02-22 16:48 ` Johan Hovold
2021-02-24 23:08 ` Joe Abbott
2021-02-25 8:44 ` Johan Hovold
[not found] ` <43da22ced8e14442bbc8babea77e4ed7@MailHC2.prolific.com.tw>
2021-02-23 10:18 ` Johan Hovold
2021-02-23 13:25 ` Michael G. Katzmann
2021-02-23 14:58 ` Michael G. Katzmann
2021-02-23 15:43 ` Johan Hovold
2021-02-23 15:57 ` Michael G. Katzmann
2021-02-23 16:14 ` Johan Hovold
2021-02-23 16:30 ` Michael G. Katzmann
2021-02-23 16:52 ` Johan Hovold
2021-02-23 19:15 ` Michael G. Katzmann
2021-02-24 17:04 ` Johan Hovold
2021-02-24 18:13 ` Michael G. Katzmann
2021-02-25 8:42 ` Johan Hovold
2021-04-08 15:35 ` Johan Hovold
2021-02-24 7:34 ` Charles Yeh
2021-02-24 17:00 ` Johan Hovold
2021-02-24 17:12 ` Michael G. Katzmann
2021-03-05 9:32 ` Charles Yeh
2021-03-05 9:36 ` Johan Hovold
2021-03-06 20:18 ` Michael G. Katzmann
2021-03-07 4:15 ` Michael G. Katzmann
2021-03-11 16:08 ` Johan Hovold
2021-03-12 13:17 ` Michael G. Katzmann
2021-03-12 13:44 ` Johan Hovold [this message]
2021-03-12 20:29 ` Michael G. Katzmann
2021-03-13 1:28 ` Michael G. Katzmann
2021-03-15 9:07 ` Johan Hovold
2021-03-15 10:07 ` Charles Yeh
2021-03-15 10:24 ` 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=YEtwNzhCmvyKhRto@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=charles-yeh@prolific.com.tw \
--cc=charlesyeh522@gmail.com \
--cc=jabbott@rollanet.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michaelk@IEEE.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).