From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 0/3] debug_ll: Cleanup conflicts for multiple SoCs
Date: Thu, 04 Jun 2026 07:55:21 +0200 [thread overview]
Message-ID: <178055252117.2196663.12286886318886273784.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260601-debug-ll-conflicts-v1-0-bf17f9f0e23a@pengutronix.de>
On Mon, 01 Jun 2026 14:29:52 +0200, Sascha Hauer wrote:
> 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.
>
> [...]
Applied, thanks!
[1/3] debug_ll: give PUTC_LL a common prototype
https://git.pengutronix.de/cgit/barebox/commit/?id=1bc53b756011 (link may not be stable)
[2/3] debug_ll: Add Kconfig options for debug uarts that have none
https://git.pengutronix.de/cgit/barebox/commit/?id=b804a356447f (link may not be stable)
[3/3] debug_ll: pl011: define PUTC_LL only when requested
https://git.pengutronix.de/cgit/barebox/commit/?id=cc145f79779f (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-06-04 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 12:29 Sascha Hauer
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 ` Sascha Hauer [this message]
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=178055252117.2196663.12286886318886273784.b4-ty@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