linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: [PATCH v2 0/2] serial: 8250: move mmp|pxa uart earlycon code and add xscale earlycon
Date: Fri, 12 Jul 2024 00:07:18 +0800	[thread overview]
Message-ID: <20240711160720.3488-1-jszhang@kernel.org> (raw)

There are two other drivers that bind to "mrvl,mmp-uart": the 8250_of
and the 8250_pxa. The previous one is generic and the latter is binded
to ARCH_PXA || ARCH_MMP. Now we may have pxa programming compatible
HW to support, making use of the generic 8250_of seems a good idea.
However, there's no earlycon support if we go with this solution. So
move the mmp|pxa-uart earlycon code to core 8250_early.c.

patch2 adds xscale earlycon support too, only build test since
I have no xscale machine any more.

Since v1:
  - split the patch into two as suggested by Greg

Jisheng Zhang (2):
  serial: 8250: move mmp|pxa uart earlycon code
  serial: 8250_early: add xscale earlycon support

 drivers/tty/serial/8250/8250_early.c | 11 +++++++++++
 drivers/tty/serial/8250/8250_pxa.c   | 16 ----------------
 2 files changed, 11 insertions(+), 16 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-07-11 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 16:07 Jisheng Zhang [this message]
2024-07-11 16:07 ` [PATCH v2 1/2] serial: 8250: move mmp|pxa uart earlycon code Jisheng Zhang
2024-07-11 16:07 ` [PATCH v2 2/2] serial: 8250_early: add xscale earlycon support Jisheng Zhang
2025-01-21 20:54 ` [PATCH v2 0/2] serial: 8250: move mmp|pxa uart earlycon code and add xscale earlycon Yixun Lan

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=20240711160720.3488-1-jszhang@kernel.org \
    --to=jszhang@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --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 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).