From: Daniel Thompson <daniel.thompson@linaro.org>
To: Russell King <linux@arm.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, spear-devel@list.st.com,
Paul Bolle <pebolle@tiscali.nl>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
John Stultz <john.stultz@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
patches@linaro.org, linaro-kernel@lists.linaro.org
Subject: [PATCH v13 9/9] arm: Fix DEBUG_LL for multi-platform kernels (without PL01X)
Date: Mon, 17 Nov 2014 14:49:10 +0000 [thread overview]
Message-ID: <1416235750-4766-10-git-send-email-daniel.thompson@linaro.org> (raw)
In-Reply-To: <1416235750-4766-1-git-send-email-daniel.thompson@linaro.org>
When building a multi_v7_defconfig kernel it is not possible to configure
DEBUG_LL to use any serial device except a ARM Primecell PL01X, or more
accurately and worse, it is possible to configure a different serial
device but KConfig does not honour this request. In fact this also
overrides the user selection for some of the single platform kernels, for
example I don't think DEBUG_LL can be targeted at ICE or semihosted
supervisor for ARCH_VERSATILE.
This happens because DEBUG_UART_PL01X is automatically enabled by
some architectures and this means user decisions made regarding
the DEBUG_LL backend will be overridden. Problem is fixed by removing the
automatic enabling of this option.
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
Acked-by: Arnd Bergmann <arnd@arndb.de>
---
arch/arm/Kconfig.debug | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
index 612bdab25f70..43a5942ed60a 100644
--- a/arch/arm/Kconfig.debug
+++ b/arch/arm/Kconfig.debug
@@ -1160,12 +1160,7 @@ config DEBUG_LL_INCLUDE
# Compatibility options for PL01x
config DEBUG_UART_PL01X
- def_bool ARCH_EP93XX || \
- ARCH_INTEGRATOR || \
- ARCH_SPEAR3XX || \
- ARCH_SPEAR6XX || \
- ARCH_SPEAR13XX || \
- ARCH_VERSATILE
+ bool
# Compatibility options for 8250
config DEBUG_UART_8250
--
1.9.3
prev parent reply other threads:[~2014-11-17 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 14:49 [PATCH v13 0/9] " Daniel Thompson
2014-11-17 14:49 ` [PATCH v13 2/9] arm: configs: Enable DEBUG_LL_UART_8250 where needed Daniel Thompson
2014-11-17 14:49 ` [PATCH v13 3/9] arm: Remove DEBUG_LL_UART_NONE Daniel Thompson
2014-11-17 14:49 ` [PATCH v13 4/9] arm: ks8695: Migrate debug_ll macros to shared directory Daniel Thompson
2014-11-17 14:49 ` [PATCH v13 5/9] arm: omap1: Migrate debug_ll macros to use 8250.S Daniel Thompson
2014-11-21 23:39 ` Tony Lindgren
2014-11-17 14:49 ` [PATCH v13 6/9] arm: netx: Migrate DEBUG_LL macros to shared directory Daniel Thompson
2014-11-17 14:49 ` [PATCH v13 7/9] arm: sa1100: " Daniel Thompson
2014-11-17 14:49 ` [PATCH v13 8/9] arm: Seperate DEBUG_UART_PHYS from DEBUG_LL on EP93XX Daniel Thompson
2014-11-17 14:49 ` Daniel Thompson [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=1416235750-4766-10-git-send-email-daniel.thompson@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=arnd@arndb.de \
--cc=john.stultz@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=patches@linaro.org \
--cc=pebolle@tiscali.nl \
--cc=spear-devel@list.st.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=sumit.semwal@linaro.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
all inboxes | Powered by JetHome®