From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 2/4] ARM: i.MX6: Riotboard: Add hint how to enable DEBUG_LL
Date: Mon, 05 Jan 2026 11:44:59 +0100 [thread overview]
Message-ID: <20260105-riotboard-v1-2-789b844d7e36@pengutronix.de> (raw)
In-Reply-To: <20260105-riotboard-v1-0-789b844d7e36@pengutronix.de>
It's not obvious which UART to chose when trying to get DEBUG_LL output
from a board. Start improving the situation by adding a comment
describing which options to enable.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
arch/arm/boards/embest-riotboard/lowlevel.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boards/embest-riotboard/lowlevel.c b/arch/arm/boards/embest-riotboard/lowlevel.c
index 3aae39f75f70601a0da7b061a5bd2b922a3e1cea..f1b37c2aa00d44ad8a2091abf21584ca531b7794 100644
--- a/arch/arm/boards/embest-riotboard/lowlevel.c
+++ b/arch/arm/boards/embest-riotboard/lowlevel.c
@@ -21,6 +21,10 @@ ENTRY_FUNCTION(start_imx6s_riotboard, r0, r1, r2)
imx6_cpu_lowlevel_init();
if (IS_ENABLED(CONFIG_DEBUG_LL)) {
+ /*
+ * CONFIG_DEBUG_IMX6Q_UART=y
+ * CONFIG_DEBUG_IMX_UART_PORT=2
+ */
writel(0x4, 0x020e016c);
imx6_ungate_all_peripherals();
imx6_uart_setup_ll();
--
2.47.3
next prev parent reply other threads:[~2026-01-05 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 10:44 [PATCH 0/4] i.MX6 Riotboard related patches Sascha Hauer
2026-01-05 10:44 ` [PATCH 1/4] ARM: i.MX6: Riotboard: ungate peripheral clocks Sascha Hauer
2026-01-05 10:44 ` Sascha Hauer [this message]
2026-01-05 10:45 ` [PATCH 3/4] gpio: Fix GPIOD_ASIS flag Sascha Hauer
2026-01-05 10:45 ` [PATCH 4/4] ARM: boards: remove #define DEBUG in board files Sascha Hauer
2026-01-06 7:46 ` (subset) [PATCH 0/4] i.MX6 Riotboard related patches Sascha Hauer
2026-01-06 7:46 ` 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=20260105-riotboard-v1-2-789b844d7e36@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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