From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "Barbier, Renaud" <renaud.barbier@abaco.com>,
"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Uart set up in PBL
Date: Thu, 4 Mar 2021 13:59:31 +0100 [thread overview]
Message-ID: <092dbc44-2081-ef3b-0fd7-25d1b9da72d3@pengutronix.de> (raw)
In-Reply-To: <MN2PR16MB3135C4186907BA49E69CD38B91979@MN2PR16MB3135.namprd16.prod.outlook.com>
Hello Renaud,
On 04.03.21 13:28, Barbier, Renaud wrote:
> Looking at many ARM platforms I see the UART is set in the PBL.
Two kinds of UART are set up in PBL:
- low level debug: DEBUG_LL
-> This is controlled via Kconfig and thus affects all
boards.
Not meant for production use
, but for very
early debugging
- PBL console: pbl_set_putc
-> This affects only a single board and each board can decide
how to set up UART beforehand. This is for when you want
regular output in PBL (e.g. because you chainload from
MMC).
> I guess the baud rate is fixed.> I am looking into a way to make the baud rate configurable.
For non-PBL, you got proper UART drivers, which can have their
baud rate configured via the baudrate device parameter, e.g.
serial1.baudrate=9600. This can come from a non-volatile variable.
> Would it possible from the PBL to read the "baudrate" variable from the environment?
Normally, you would want to avoid doing anything, but the
bare minimum from PBL. Does the baudrate device parameter
work for you?
Cheers,
Ahmad
>
> Cheers,
> Renaud
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
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
next prev parent reply other threads:[~2021-03-04 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 12:28 Barbier, Renaud
2021-03-04 12:59 ` Ahmad Fatoum [this message]
2021-03-04 16:41 ` Barbier, Renaud
2021-03-05 10:48 ` Ahmad Fatoum
2021-03-05 13:08 ` Barbier, Renaud
2021-03-08 20:22 ` Ahmad Fatoum
2021-03-04 13:07 ` Sascha Hauer
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=092dbc44-2081-ef3b-0fd7-25d1b9da72d3@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=renaud.barbier@abaco.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