From: Jay Dolan <jay.dolan@accesio.com>
To: linux-serial@vger.kernel.org
Cc: Jay Dolan <jay.dolan@accesio.com>
Subject: [PATCH 0/3] serial: 8250_pci patches to address issues with pericom_do_set_divisor()
Date: Sun, 14 Nov 2021 10:39:05 -0800 [thread overview]
Message-ID: <20211114183908.444923-1-jay.dolan@accesio.com> (raw)
A series patches to address three issues one customer managed to hit all at once.
1) Rewrite pericom_do_set_divisor() to always calc divisor and to use the
uartclk instead of a hard coded value. Always calculate divisor without passing
control to serial8250_do_set_divisor()
Tested with 14.7456 and 24 MHz crystals
2) Re-enable higher baud rates on Pericom chips.
serial8250_get_baud_rate() added range checking, but Pericom chips have a wider
range than what is being enforced. Make use of UPF_MAGIC_MULTIPLIER.
Tested with 14.7456 and 24 MHz crystals
3) Fourth port not being setup correctly on some Pericom chips.
Fix entries in pci_serial_quirks array
Jay Dolan (3):
serial: 8250_pci: rewrite pericom_do_set_divisor
serial: 8250_pci: Re-enable higher baud rates on Pericom chips
serial: 8250_pci: Fix ACCES entries in pci_serial_quirks array
drivers/tty/serial/8250/8250_pci.c | 44 +++++++++++++++++++++---------
1 file changed, 31 insertions(+), 13 deletions(-)
--
2.25.1
next reply other threads:[~2021-11-14 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 18:39 Jay Dolan [this message]
2021-11-14 18:39 ` [PATCH 1/3] serial: 8250_pci: rewrite pericom_do_set_divisor Jay Dolan
2021-11-25 17:30 ` Greg KH
2021-11-14 18:39 ` [PATCH 2/3] serial: 8250_pci: Re-enable higher baud rates on Pericom chips Jay Dolan
2021-11-16 15:31 ` Andy Shevchenko
2021-11-14 18:39 ` [PATCH 3/3] serial: 8250_pci: Fix ACCES entries in pci_serial_quirks array Jay Dolan
2021-11-16 15:31 ` Andy Shevchenko
2021-11-16 15:34 ` [PATCH 0/3] serial: 8250_pci patches to address issues with pericom_do_set_divisor() Andy Shevchenko
2021-11-17 3:52 ` Jay Dolan
2021-11-17 13:24 ` Andy Shevchenko
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=20211114183908.444923-1-jay.dolan@accesio.com \
--to=jay.dolan@accesio.com \
--cc=linux-serial@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.