From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH master 3/4] ARM: k3: define debug_ll_write_reg only on CONFIG_DEBUG_AM62X_UART=y
Date: Tue, 22 Apr 2025 16:23:12 +0200 [thread overview]
Message-ID: <aAemUHavn4l7YBkY@pengutronix.de> (raw)
In-Reply-To: <20250422075519.219029-3-a.fatoum@pengutronix.de>
On Tue, Apr 22, 2025 at 09:55:18AM +0200, Ahmad Fatoum wrote:
> From: Ahmad Fatoum <a.fatoum@barebox.org>
>
> Defining debug_ll_read_reg unconditionally for K3 can clash with other
> debug_ll implementations, so move it into the include guard.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
> ---
> include/mach/k3/debug_ll.h | 37 ++++++++++++++++++-------------------
> 1 file changed, 18 insertions(+), 19 deletions(-)
This breaks compilation of multi_v8_defconfig:
arch/arm/boards/beagleplay/lowlevel.c:44:30: error: debug_ll_ns16550_putc' undeclared (first use in this function)
44 | pbl_set_putc((void *)debug_ll_ns16550_putc, (void *)AM62X_UART_UART0_BASE);
debug_ll_ns16550_putc() is used as the pbl putc function. This might
have been wrong from the start, but it is like it is.
Not sure what we should do about it. We would need some ns16550 putc
function that is independent of the debug_ll infrastructure.
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-04-22 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 7:55 [PATCH master 1/4] KASan: fix possible breakage with CONFIG_INIT_STACK_ALL Ahmad Fatoum
2025-04-22 7:55 ` [PATCH master 2/4] ARM: Layerscape: fix compilation of LS1028 without LS1046 Ahmad Fatoum
2025-04-22 14:14 ` Sascha Hauer
2025-04-22 14:18 ` Ahmad Fatoum
2025-04-22 7:55 ` [PATCH master 3/4] ARM: k3: define debug_ll_write_reg only on CONFIG_DEBUG_AM62X_UART=y Ahmad Fatoum
2025-04-22 14:23 ` Sascha Hauer [this message]
2025-04-22 14:29 ` Ahmad Fatoum
2025-04-22 14:34 ` Sascha Hauer
2025-04-22 7:55 ` [PATCH master 4/4] memory: correct return value in request_barebox_region stub Ahmad Fatoum
2025-04-22 9:29 ` [PATCH master 1/4] KASan: fix possible breakage with CONFIG_INIT_STACK_ALL 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=aAemUHavn4l7YBkY@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@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