From: Sascha Hauer <s.hauer@pengutronix.de>
To: Lucas Stach <dev@lynxeye.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: MXS: duckbill: set duart to serial0
Date: Wed, 3 Jun 2020 10:20:50 +0200 [thread overview]
Message-ID: <20200603082050.GW11869@pengutronix.de> (raw)
In-Reply-To: <81baec3b23d148e9085bb73b28c52dd1f9ba818f.camel@lynxeye.de>
On Fri, May 29, 2020 at 03:56:53PM +0200, Lucas Stach wrote:
> Am Freitag, den 29.05.2020, 14:51 +0200 schrieb Michael Grzeschik:
> > In the imx28.dtsi the serial0 is set to auart0 which is not the one
> > used on the duckbill. We set duart to serial0 so the console will be
> > properly set.
>
> If the aliases are the same in the Barebox and Linux DTs there should
> be no need to override the alias numbering in the individual board DTs.
>
> Is the Linux driver ignoring the alias, or what is the issue being
> fixed here?
There are two different UARTs on the i.MX23/28, the duart ends up as
ttyAMAx in the kernel, the auart as ttyAPPx. Both drivers honor the
alias in the device tree. The upstream dtsi has:
serial0 = &auart0;
serial1 = &auart1;
serial2 = &auart2;
serial3 = &auart3;
serial4 = &auart4;
With this we can't assign an alias to the duart anymore, serial0 is
already used. We could add a serial5 alias, but then we would get
ttyAMA5 instead of the desired ttyAMA0.
barebox tries to get an alias for the duart to set the proper console=
string for it. Now Michael changes the serial0 alias from &auart0 to
&duart. With this barebox can assign the correct console= string. Would
Linux be started with this device tree, &auart0 would still end up with
ttyAPP0 because it's the first free one.
This looks awful, but works for now. We are open for better suggestions
;)
Regards,
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2020-06-03 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 12:51 Michael Grzeschik
2020-05-29 13:56 ` Lucas Stach
2020-06-02 12:02 ` Michael Grzeschik
2020-06-03 8:20 ` Sascha Hauer [this message]
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=20200603082050.GW11869@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=dev@lynxeye.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