LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Cc: Jiri Slaby <jirislaby@kernel.org>, Jay Dolan <jay.dolan@accesio.com>
Subject: [PATCH v2 0/3] serial: 8250_pci: Split Pericom driver
Date: Mon, 22 Nov 2021 15:35:09 +0200 [thread overview]
Message-ID: <20211122133512.8947-1-andriy.shevchenko@linux.intel.com> (raw)
Split Pericom driver to a separate module.
While at it, re-enable high baud rates.
Jay, can you, please, test this on as many hardware as you have?
The series depends on the fix-series:
https://lore.kernel.org/linux-serial/20211122120604.3909-1-andriy.shevchenko@linux.intel.com/T/#u
Changelog v2:
- rebased on top of v3 of the fix-series (see above)
- added new patch 3
Andy Shevchenko (2):
serial: 8250_pci: Split out Pericom driver
serial: 8250_pericom: Use serial_dl_write() instead of open coded
Jay Dolan (1):
serial: 8250_pericom: Re-enable higher baud rates
drivers/tty/serial/8250/8250_pci.c | 405 +------------------------
drivers/tty/serial/8250/8250_pericom.c | 214 +++++++++++++
drivers/tty/serial/8250/Kconfig | 8 +
drivers/tty/serial/8250/Makefile | 1 +
4 files changed, 228 insertions(+), 400 deletions(-)
create mode 100644 drivers/tty/serial/8250/8250_pericom.c
--
2.33.0
next reply other threads:[~2021-11-22 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 13:35 Andy Shevchenko [this message]
2021-11-22 13:35 ` [PATCH v2 1/3] serial: 8250_pci: Split out " Andy Shevchenko
2021-11-22 13:35 ` [PATCH v2 2/3] serial: 8250_pericom: Re-enable higher baud rates Andy Shevchenko
2021-11-22 13:35 ` [PATCH v2 3/3] serial: 8250_pericom: Use serial_dl_write() instead of open coded Andy Shevchenko
2021-11-23 5:27 ` Jay Dolan
2021-11-23 9:00 ` 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=20211122133512.8947-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jay.dolan@accesio.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--subject='Re: [PATCH v2 0/3] serial: 8250_pci: Split Pericom driver' \
/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
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).