linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@nxp.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"jslaby@suse.com" <jslaby@suse.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>, Alice Guo <alice.guo@nxp.com>,
	Peng Fan <peng.fan@nxp.com>
Subject: [PATCH V2 0/3] tty: serial: lpuart: cleanup and improve for earlycon
Date: Fri, 20 Dec 2019 06:13:30 +0000	[thread overview]
Message-ID: <1576822230-23125-1-git-send-email-peng.fan@nxp.com> (raw)

From: Peng Fan <peng.fan@nxp.com>

V2:
  Drop a wrong patch which should not be included in this patchset,
  nothing else changed.

EARLYCON_DECLARE could be dropped, since OF_EARLYCON_DECLARE does same.

i.MX8QXP is compatible with i.MX7ULP, no need an extra entry.

When we could not use stdout-path for earlycon for i.MX8QXP,
we need pass mmio32 to earlycon, so update code to support the iotype.

Peng Fan (3):
  tty: serial: fsl_lpuart: drop EARLYCON_DECLARE
  tty: serial: fsl_lpuart: support UPIO_MEM32 for lpuart32
  tty: serial: fsl_lpuart: drop earlycon entry for i.MX8QXP

 drivers/tty/serial/fsl_lpuart.c | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

-- 
2.16.4


             reply	other threads:[~2019-12-20  6:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20  6:13 Peng Fan [this message]
2019-12-20  6:13 ` [PATCH V2 1/3] tty: serial: fsl_lpuart: drop EARLYCON_DECLARE Peng Fan
2019-12-20  6:13 ` [PATCH V2 2/3] tty: serial: fsl_lpuart: support UPIO_MEM32 for lpuart32 Peng Fan
2019-12-20  6:13 ` [PATCH V2 3/3] tty: serial: fsl_lpuart: drop earlycon entry for i.MX8QXP Peng Fan

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=1576822230-23125-1-git-send-email-peng.fan@nxp.com \
    --to=peng.fan@nxp.com \
    --cc=alice.guo@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.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).