From: Erwan Le Ray <erwan.leray@st.com>
To: Russell King <linux@armlinux.org.uk>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
Olof Johansson <olof@lixom.net>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Nathan Huckleberry <nhuck15@gmail.com>,
Gerald Baeza <gerald.baeza@st.com>,
Erwan Le Ray <erwan.leray@st.com>,
Clement Peron <peron.clem@gmail.com>,
Fabrice Gasnier <fabrice.gasnier@st.com>
Subject: [PATCH v3 2/4] ARM: debug: stm32: add UART early console configuration for STM32F7
Date: Mon, 3 Feb 2020 15:04:23 +0100 [thread overview]
Message-ID: <20200203140425.26579-3-erwan.leray@st.com> (raw)
In-Reply-To: <20200203140425.26579-1-erwan.leray@st.com>
Early console is hardcoded on USART1 in current implementation.
With this patch, default UART instance is USART1, but other UART instances
can be configured by setting physical and virtual base addresses in
menuconfig.
Signed-off-by: Erwan Le Ray <erwan.leray@st.com>
diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
index 4f982ef1d0ec..5ff66c294a5a 100644
--- a/arch/arm/Kconfig.debug
+++ b/arch/arm/Kconfig.debug
@@ -1213,12 +1213,13 @@ choice
config STM32F7_DEBUG_UART
bool "Use STM32F7 UART for low-level debug"
- depends on ARCH_STM32
+ depends on MACH_STM32F746 || MACH_STM32F769
select DEBUG_STM32_UART
help
Say Y here if you want kernel low-level debugging support
on STM32F7 based platforms, which default UART is wired on
- USART1.
+ USART1, but another UART instance can be selected by modifying
+ CONFIG_DEBUG_UART_PHYS.
If unsure, say N.
@@ -1620,7 +1621,7 @@ config DEBUG_UART_PHYS
default 0x3e000000 if DEBUG_BCM_KONA_UART
default 0x3f201000 if DEBUG_BCM2836
default 0x4000e400 if DEBUG_LL_UART_EFM32
- default 0x40011000 if STM32F4_DEBUG_UART
+ default 0x40011000 if STM32F4_DEBUG_UART || STM32F7_DEBUG_UART
default 0x40028000 if DEBUG_AT91_SAMV7_USART1
default 0x40081000 if DEBUG_LPC18XX_UART0
default 0x40090000 if DEBUG_LPC32XX
--
2.17.1
next prev parent reply other threads:[~2020-02-03 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 14:04 [PATCH v3 0/4] STM32 early console Erwan Le Ray
2020-02-03 14:04 ` [PATCH v3 1/4] ARM: debug: stm32: add UART early console configuration for STM32F4 Erwan Le Ray
2020-02-03 14:04 ` Erwan Le Ray [this message]
2020-02-03 14:04 ` [PATCH v3 3/4] ARM: debug: stm32: add UART early console support for STM32H7 Erwan Le Ray
2020-02-03 14:04 ` [PATCH v3 4/4] ARM: debug: stm32: add UART early console support for STM32MP1 Erwan Le Ray
2020-02-03 14:35 ` [PATCH v3 0/4] STM32 early console Clément Péron
2020-02-21 15:54 ` Erwan LE RAY
2020-02-21 15:58 ` Alexandre Torgue
2020-02-22 11:22 ` Linus Walleij
2020-03-13 12:56 ` Alexandre Torgue
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=20200203140425.26579-3-erwan.leray@st.com \
--to=erwan.leray@st.com \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=fabrice.gasnier@st.com \
--cc=geert+renesas@glider.be \
--cc=gerald.baeza@st.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=nhuck15@gmail.com \
--cc=olof@lixom.net \
--cc=peron.clem@gmail.com \
--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
all inboxes | Powered by JetHome®