From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: linux-serial@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: linux-kernel@vger.kernel.org,
"Niklas Schnelle" <schnelle@linux.ibm.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: [PATCH v3 0/6] serial: Separate RT288x/Au1xxx code into own file
Date: Tue, 9 May 2023 14:39:18 +0300 [thread overview]
Message-ID: <20230509113924.19540-1-ilpo.jarvinen@linux.intel.com> (raw)
A non-trivial amount of RT288x/Au1xxx code is encapsulated into
ifdeffery in 8250_port / 8250_early and some if/switch UPIO_AU blocks.
Create a separate file from them and do a few additional cleanups.
I kept the Kconfig entry as bool because the code has somewhat tricky
dependency chain (mips arch code and 8250_of driver).
v3:
- Convert dl_read/write() to take u32 arg + name the args
- Separatate the non-driver datastructure changes & document them better
- Fix build when SERIAL_8250=m + SERIAL_8250_RT288X=y (+note reasoning
in the commit message for future reference)
- Use u8 for arrays that no longer have < 0 values
v2:
- Define register map array lengths explicitly to avoid creating
declaration trap.
Ilpo Järvinen (6):
serial: 8250: Change dl_read/write to handle value as u32
serial: 8250: Document uart_8250_port's ->dl_read/write()
serial: 8250: Add dl_read/write, bugs and mapsize into plat_serial8250_port
serial: 8250: RT288x/Au1xxx code away from core
serial: 8250_rt288x: Name non-standard divisor latch reg
serial: 8250_rt288x: Remove unnecessary UART_REG_UNMAPPED
arch/mips/alchemy/common/platform.c | 10 +-
drivers/tty/serial/8250/8250.h | 4 +-
drivers/tty/serial/8250/8250_core.c | 4 +
drivers/tty/serial/8250/8250_early.c | 21 ----
drivers/tty/serial/8250/8250_em.c | 4 +-
drivers/tty/serial/8250/8250_of.c | 4 +-
drivers/tty/serial/8250/8250_port.c | 84 +--------------
drivers/tty/serial/8250/8250_pxa.c | 2 +-
drivers/tty/serial/8250/8250_rt288x.c | 136 ++++++++++++++++++++++++
drivers/tty/serial/8250/8250_uniphier.c | 4 +-
drivers/tty/serial/8250/Makefile | 1 +
drivers/tty/serial/Makefile | 2 +-
include/linux/serial_8250.h | 42 +++++++-
13 files changed, 200 insertions(+), 118 deletions(-)
create mode 100644 drivers/tty/serial/8250/8250_rt288x.c
--
2.30.2
next reply other threads:[~2023-05-09 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 11:39 Ilpo Järvinen [this message]
2023-05-09 11:39 ` [PATCH v3 1/6] serial: 8250: Change dl_read/write to handle value as u32 Ilpo Järvinen
2023-05-10 5:47 ` Jiri Slaby
2023-05-09 11:39 ` [PATCH v3 2/6] serial: 8250: Document uart_8250_port's ->dl_read/write() Ilpo Järvinen
2023-05-09 11:39 ` [PATCH v3 3/6] serial: 8250: Add dl_read/write, bugs and mapsize into plat_serial8250_port Ilpo Järvinen
2023-05-10 5:55 ` Jiri Slaby
2023-05-09 11:39 ` [PATCH v3 4/6] serial: 8250: RT288x/Au1xxx code away from core Ilpo Järvinen
2023-05-09 11:39 ` [PATCH v3 5/6] serial: 8250_rt288x: Name non-standard divisor latch reg Ilpo Järvinen
2023-05-09 11:39 ` [PATCH v3 6/6] serial: 8250_rt288x: Remove unnecessary UART_REG_UNMAPPED Ilpo Järvinen
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=20230509113924.19540-1-ilpo.jarvinen@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=philmd@linaro.org \
--cc=schnelle@linux.ibm.com \
/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
all inboxes | Powered by JetHome®