From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Fabian Pflug <f.pflug@pengutronix.de>,
barebox@lists.infradead.org, maud_spierings@hotmail.com
Subject: Re: [PATCH v2 2/2] ARM: boards: i.MX93: Add NXP FRDM i.MX93 support
Date: Wed, 22 Oct 2025 08:52:39 +0200 [thread overview]
Message-ID: <aPh_N1eMfstGMgbY@pengutronix.de> (raw)
In-Reply-To: <22735bfd-c673-45ec-8b98-4bb4ae6cfad0@pengutronix.de>
On Tue, Oct 21, 2025 at 01:11:46PM +0200, Ahmad Fatoum wrote:
> > +static noinline void frdm_imx93_continue(void)
> > +{
> > + void __iomem *base = IOMEM(MX9_UART1_BASE_ADDR);
> > + void __iomem *muxbase = IOMEM(MX9_IOMUXC_BASE_ADDR);
> > +
> > + /* configure LPUART1 TX pin */
> > + writel(0x0, muxbase + 0x184);
> > +
> > + imx9_uart_setup(base);
> > + pbl_set_putc(lpuart32_putc, base + 0x10);
> > + putchar('>');
>
> Do you see the > character on bootup if CONFIG_PBL_CONSOLE is enabled?
> Maud (Cc'd) mentioned on the IRC that the 0x10 offset shouldn't be
> necessary.
The UART register space starts at offset 0x10 from the base address.
Some Layerscape SoCs use the same lpuart implementation without this
offset (although barebox doesn't have support for these Layerscape
SoCs).
Maybe we could add a
static inline void imx93_uart_putc(void __iomem *base)
{
lpuart32_putc(base + 0x10);
}
to avoid confusion.
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 |
next prev parent reply other threads:[~2025-10-22 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 11:42 [PATCH] " Fabian Pflug
2025-05-27 12:23 ` Marco Felsch
2025-05-27 12:37 ` Ahmad Fatoum
2025-10-21 10:59 ` [PATCH v2 0/2] " Fabian Pflug
2025-10-21 10:59 ` [PATCH v2 1/2] common: deep-probe: include of for of_device_id Fabian Pflug
2025-10-21 10:59 ` [PATCH v2 2/2] ARM: boards: i.MX93: Add NXP FRDM i.MX93 support Fabian Pflug
2025-10-21 11:11 ` Ahmad Fatoum
2025-10-21 11:37 ` Fabian Pflug
2025-10-21 11:43 ` Ahmad Fatoum
2025-10-21 11:53 ` Fabian Pflug
2025-10-21 11:58 ` Maud Spierings
2025-10-22 6:52 ` Sascha Hauer [this message]
2025-10-21 18:01 ` [PATCH v2 0/2] " Maud Spierings
2025-10-22 6:47 ` 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=aPh_N1eMfstGMgbY@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=f.pflug@pengutronix.de \
--cc=maud_spierings@hotmail.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