From: Michael Tretter <m.tretter@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Michael Tretter <m.tretter@pengutronix.de>
Subject: [PATCH 0/3] arm: socfpga: cleanup UART for serial console
Date: Fri, 05 Jun 2026 14:58:12 +0200 [thread overview]
Message-ID: <20260605-socfpga-debug-uart-v1-0-8454bfc709bf@pengutronix.de> (raw)
Configuring debug console output for the PBL and low level code on
SoCFPGA boards is surprisingly complex and an inconsistent configuration
bit me more than once.
Get rid of the custom UART implementation and the base addresses for the
debug UART in the barebox configuration.
While at it, set the debug UART for the Arrow AXE5 board in the board
code and don't force the developer to know and configure the correct
debug UART in the configuration.
Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
---
Michael Tretter (3):
arm: socfpga: replace custom UART with ns16550
arm: socfpga: get rid of UART address for low-level debug
arm: socfpga: axe5-eagle: always use UART0
arch/arm/boards/arrow-axe5-eagle/lowlevel.c | 6 +-
common/Kconfig.debug_ll | 44 +++--------
include/mach/socfpga/debug_ll.h | 113 +++++++++++-----------------
3 files changed, 57 insertions(+), 106 deletions(-)
---
base-commit: 713a1e59dfea4516446822323b7c0db571cb214f
change-id: 20260605-socfpga-debug-uart-d840aa594751
Best regards,
--
Michael Tretter <m.tretter@pengutronix.de>
next reply other threads:[~2026-06-05 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 12:58 Michael Tretter [this message]
2026-06-05 12:58 ` [PATCH 1/3] arm: socfpga: replace custom UART with ns16550 Michael Tretter
2026-06-05 12:58 ` [PATCH 2/3] arm: socfpga: get rid of UART address for low-level debug Michael Tretter
2026-06-05 12:58 ` [PATCH 3/3] arm: socfpga: axe5-eagle: always use UART0 Michael Tretter
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=20260605-socfpga-debug-uart-v1-0-8454bfc709bf@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@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