From: Maud Spierings <maud_spierings@hotmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Fabian Pflug <f.pflug@pengutronix.de>,
barebox@lists.infradead.org
Subject: Re: [PATCH v2 2/2] ARM: boards: i.MX93: Add NXP FRDM i.MX93 support
Date: Tue, 21 Oct 2025 13:58:43 +0200 [thread overview]
Message-ID: <AM7P189MB1009344F5A203A260220773AE3F2A@AM7P189MB1009.EURP189.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <f71d6e88-32f7-46ab-97ff-b417848377b3@pengutronix.de>
On 10/21/25 13:43, Ahmad Fatoum wrote:
> Hello Fabian,
>
> On 10/21/25 1:37 PM, Fabian Pflug wrote:
>> Hello Ahmad,
>>
>> On Tue, 2025-10-21 at 13:11 +0200, Ahmad Fatoum wrote:
>>> Hello Fabian,
>>>
>>>> +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.
>>>
>>
>> I did see the > character with (working with a 2025.07.0 barebox here):
>
> Ok, good to know.
>
>
>> But there seems to be another Problem. If I enable
>>
>> CONFIG_DEBUG_LL=y
>> CONFIG_DEBUG_IMX_UART=y
>> CONFIG_DEBUG_IMX8M_UART=y
>> CONFIG_DEBUG_IMX_UART_PORT=1
>> CONFIG_DEBUG_PBL=y
>
> Given that you are using the i.MX9's LPUART, I think it's expected that
> DEBUG_LL misbehaves. PBL output works, because the PBL console has
> precedence over DEBUG_LL.
>
> Cheers,
> Ahmad
>
I think I may have confused something.
Could've sworn I saw the base + 0x10 in the _uart_setup() call, but now
that I am looking at it again I don't see it.
I may have been a bit too tired yesterday and made a premature
conclusion, based on incorrectly reading the code.
Kind regards,
Maud
next prev parent reply other threads:[~2025-10-21 12:06 UTC|newest]
Thread overview: 12+ 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 [this message]
2025-10-21 18:01 ` [PATCH v2 0/2] " Maud Spierings
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=AM7P189MB1009344F5A203A260220773AE3F2A@AM7P189MB1009.EURP189.PROD.OUTLOOK.COM \
--to=maud_spierings@hotmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=f.pflug@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