From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 0/3] debug_ll: Cleanup conflicts for multiple SoCs
Date: Mon, 01 Jun 2026 14:29:52 +0200 [thread overview]
Message-ID: <20260601-debug-ll-conflicts-v1-0-bf17f9f0e23a@pengutronix.de> (raw)
This cleans up some problems we have with debug_ll when it comes to
multi SoC images. debug_ll relies on having exactly one PUTC_LL()
implementation available. Most SoCs have their own DEBUG_*_UART Kconfig
option and the Kconfig choice around them makes sure only a single debug
UART can be selected. Some SoCs do not have a dedicated option though
and provide PUTC_LL() whenever the SoC is enabled which can to multiple
definitions of PUTC_LL(). Fix that by adding a DEBUG_*_UART option to
the SoC that currently do not have one.
Another problem is that pl011.h provides PUTC_LL() and
debug_ll_pl011_putc(). The former is needed when included indirectly
from debug_ll.h, the latter is needed by board code to specify a putc()
to the PBL console. This too ends up in multiple definitions of
PUTC_LL().
Both problems are fixed in this series
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (3):
debug_ll: give PUTC_LL a common prototype
debug_ll: Add Kconfig options for debug uarts that have none
debug_ll: pl011: define PUTC_LL only when requested
arch/arm/include/asm/debug_ll.h | 69 ++++++++--------------
.../mips/mach-ath79/include/mach/debug_ll_ar9331.h | 2 +-
arch/openrisc/include/asm/debug_ll.h | 2 +-
arch/powerpc/include/asm/debug_ll.h | 2 +-
common/Kconfig.debug_ll | 28 +++++++++
include/debug_ll.h | 2 +
include/debug_ll/pl011.h | 6 +-
include/mach/bcm283x/debug_ll.h | 4 +-
include/mach/imx/debug_ll.h | 2 +-
include/mach/k3/debug_ll.h | 2 +-
include/mach/layerscape/debug_ll.h | 2 +-
include/mach/mxs/debug_ll.h | 2 +-
include/mach/omap/debug_ll.h | 2 +-
include/mach/rockchip/debug_ll.h | 2 +-
include/mach/stm32mp/debug_ll.h | 2 +-
include/mach/zynq/debug_ll.h | 2 +-
include/mach/zynqmp/debug_ll.h | 2 +-
17 files changed, 69 insertions(+), 64 deletions(-)
---
base-commit: 81fbe2e8d0d445032498a0bfecf9fd270f00985a
change-id: 20260601-debug-ll-conflicts-a5aeab40b99b
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2026-06-01 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 12:29 Sascha Hauer [this message]
2026-06-01 12:29 ` [PATCH 1/3] debug_ll: give PUTC_LL a common prototype Sascha Hauer
2026-06-01 12:29 ` [PATCH 2/3] debug_ll: Add Kconfig options for debug uarts that have none Sascha Hauer
2026-06-01 12:29 ` [PATCH 3/3] debug_ll: pl011: define PUTC_LL only when requested Sascha Hauer
2026-06-04 5:55 ` [PATCH 0/3] debug_ll: Cleanup conflicts for multiple SoCs 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=20260601-debug-ll-conflicts-v1-0-bf17f9f0e23a@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