devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Saravana Kannan <saravanak@google.com>
Cc: "Sascha Hauer" <s.hauer@pengutronix.de>,
	"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"NXP Linux Team" <linux-imx@nxp.com>,
	hvilleneuve@dimonoff.com, "Lucas Stach" <l.stach@pengutronix.de>,
	abbaraju.manojsai@amarulasolutions.com,
	"Jagan Teki" <jagan@amarulasolutions.com>,
	"Matteo Lisi" <matteo.lisi@engicam.com>,
	"Tim Harvey" <tharvey@gateworks.com>,
	"Teresa Remmet" <t.remmet@phytec.de>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	t.remmet@phytec.deh,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Peng Fan" <peng.fan@nxp.com>
Subject: Re: [PATCH] arm64: dts: imx8mp: drop dmas property for uart console
Date: Thu, 23 Jun 2022 17:51:31 -0300	[thread overview]
Message-ID: <CAOMZO5BvnBCza5HQVNUQqDBZR9WsXiK4RuVPh654GJGb2jw+1g@mail.gmail.com> (raw)
In-Reply-To: <CAGETcx-_nwrzJzaY3yc80g4AfydV5J9-JYE5h1m+5TT05jyKOw@mail.gmail.com>

On Thu, Jun 23, 2022 at 3:58 PM Saravana Kannan <saravanak@google.com> wrote:

> Will do. I'm looking at the serial console code and I don't see a
> difference between earlycon= vs console= handling. And I know that
> earlycon= doesn't go through the driver core and isn't affected by any
> of this. If you have additional pointers on where console= is parsed,
> feel free to pass it on. I'll continue poking at this.

It seems to be parsed at uart_parse_earlycon() inside
drivers/tty/serial/serial_core.c.

  reply	other threads:[~2022-06-23 20:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  6:20 [PATCH] arm64: dts: imx8mp: drop dmas property for uart console Peng Fan (OSS)
2022-06-22  7:24 ` Sascha Hauer
2022-06-22 22:31   ` Saravana Kannan
2022-06-22 22:33     ` Peng Fan
2022-06-23 11:35     ` Fabio Estevam
2022-06-23 18:20       ` Fabio Estevam
2022-06-23 18:25         ` Saravana Kannan
2022-06-23 18:43           ` Fabio Estevam
2022-06-23 18:58             ` Saravana Kannan
2022-06-23 20:51               ` Fabio Estevam [this message]
2022-06-23 21:28                 ` Saravana Kannan
2022-06-25  7:15   ` Saravana Kannan
2022-06-27  8:22     ` Peng Fan (OSS)
2022-06-28  3:00       ` Saravana Kannan

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=CAOMZO5BvnBCza5HQVNUQqDBZR9WsXiK4RuVPh654GJGb2jw+1g@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=abbaraju.manojsai@amarulasolutions.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hvilleneuve@dimonoff.com \
    --cc=jagan@amarulasolutions.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matteo.lisi@engicam.com \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=saravanak@google.com \
    --cc=shawnguo@kernel.org \
    --cc=t.remmet@phytec.de \
    --cc=t.remmet@phytec.deh \
    --cc=tharvey@gateworks.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).