U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: me@samcday.com
Cc: u-boot@lists.denx.de, Sumit Garg <sumit.garg@kernel.org>,
	u-boot-qcom@groups.io, Tom Rini <trini@konsulko.com>,
	Dmitrii Sharshakov <d3dx12.xx@gmail.com>,
	Brian Sune <briansune@gmail.com>,
	Casey Connolly <casey.connolly@linaro.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Simon Glass <sjg@chromium.org>,
	Kuan-Wei Chiu <visitorckw@gmail.com>,
	Daniel Palmer <daniel@0x0f.com>,
	Luca Weiss <luca.weiss@fairphone.com>,
	Quentin Schulz <quentin.schulz@cherry.de>, Yao Zi <me@ziyao.cc>
Subject: Re: [PATCH v2] mach-snapdragon: formalize APQ8016 debug UART init
Date: Wed, 10 Jun 2026 15:09:30 +0200	[thread overview]
Message-ID: <ailiCiJ1aJDMimyb@linaro.org> (raw)
In-Reply-To: <20260610-apq8016-debug-uart-v2-1-acf43d28add6@samcday.com>

On Wed, Jun 10, 2026 at 11:57:20AM +1000, Sam Day via B4 Relay wrote:
> From: Sam Day <me@samcday.com>
> 
> The dragonboard410c (and likely other SB-off devices) can run U-Boot
> early enough in the boot chain such that UART clock isn't started, and
> pins aren't configured.
> 
> APQ8016 has two UART peripherals, each with its own clock and TLMM pins.
> 
> Two new debug-apq8016-uartN.config fragments are provided. Each
> configures the appropriate UARTDM aperture. The newly introduced
> DEBUG_UART_APQ8016 Kconfig symbol pulls in MSM debug UART, and enables a
> board-level debug_uart_init function to start the right clock and mux
> the right TX pin.
> 
> Signed-off-by: Sam Day <me@samcday.com>
> ---
> Changes in v2:
> - Rename APQ8016_TLMM_GPIO_ENABLE to APQ8016_TLMM_GPIO_OE
> - Link to v1: https://lore.kernel.org/r/20260603-apq8016-debug-uart-v1-1-1e46b2cd0fe6@samcday.com
> ---
>  arch/arm/mach-snapdragon/Kconfig              |  9 +++++++
>  arch/arm/mach-snapdragon/Makefile             |  1 +
>  arch/arm/mach-snapdragon/debug-uart-apq8016.c | 37 +++++++++++++++++++++++++++
>  board/qualcomm/debug-apq8016-uart1.config     |  4 +++
>  board/qualcomm/debug-apq8016-uart2.config     |  4 +++
>  drivers/serial/Kconfig                        |  1 +
>  drivers/serial/serial_msm.c                   | 10 --------
>  7 files changed, 56 insertions(+), 10 deletions(-)
> 
> diff --git a/arch/arm/mach-snapdragon/Kconfig b/arch/arm/mach-snapdragon/Kconfig
> index d3de8693b5a..43e6fd1bc42 100644
> --- a/arch/arm/mach-snapdragon/Kconfig
> +++ b/arch/arm/mach-snapdragon/Kconfig
> @@ -1,5 +1,14 @@
>  if ARCH_SNAPDRAGON
>  
> +config DEBUG_UART_APQ8016
> +	bool "APQ8016 early debug initialization"
> +	select CLK_QCOM_APQ8016
> +	select CONFIG_DEBUG_UART_MSM

Should we have the CONFIG_ prefix here in Kconfig? Not sure if both
works, but I'd expect this isn't required/typical here.

Thanks,
Stephan

      reply	other threads:[~2026-06-10 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  1:57 [PATCH v2] mach-snapdragon: formalize APQ8016 debug UART init Sam Day via B4 Relay
2026-06-10 13:09 ` Stephan Gerhold [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=ailiCiJ1aJDMimyb@linaro.org \
    --to=stephan.gerhold@linaro.org \
    --cc=briansune@gmail.com \
    --cc=casey.connolly@linaro.org \
    --cc=d3dx12.xx@gmail.com \
    --cc=daniel@0x0f.com \
    --cc=luca.weiss@fairphone.com \
    --cc=me@samcday.com \
    --cc=me@ziyao.cc \
    --cc=neil.armstrong@linaro.org \
    --cc=quentin.schulz@cherry.de \
    --cc=sjg@chromium.org \
    --cc=sumit.garg@kernel.org \
    --cc=trini@konsulko.com \
    --cc=u-boot-qcom@groups.io \
    --cc=u-boot@lists.denx.de \
    --cc=visitorckw@gmail.com \
    /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