From: Max Filippov <jcmvbkbc@gmail.com>
To: linux-xtensa@linux-xtensa.org, linux-kernel@vger.kernel.org
Cc: Chris Zankel <chris@zankel.net>, Marc Gauthier <marc@cadence.com>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: [PATCH 1/8] xtensa: clean up Kconfig dependencies for custom cores
Date: Mon, 6 Jul 2015 16:32:42 +0300 [thread overview]
Message-ID: <1436189569-28802-2-git-send-email-jcmvbkbc@gmail.com> (raw)
In-Reply-To: <1436189569-28802-1-git-send-email-jcmvbkbc@gmail.com>
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
---
arch/xtensa/Kconfig | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/arch/xtensa/Kconfig b/arch/xtensa/Kconfig
index 87be10e..ba22699 100644
--- a/arch/xtensa/Kconfig
+++ b/arch/xtensa/Kconfig
@@ -61,9 +61,7 @@ config TRACE_IRQFLAGS_SUPPORT
def_bool y
config MMU
- bool
- default n if !XTENSA_VARIANT_CUSTOM
- default XTENSA_VARIANT_MMU if XTENSA_VARIANT_CUSTOM
+ def_bool n
config VARIANT_IRQ_SWITCH
def_bool n
@@ -71,9 +69,6 @@ config VARIANT_IRQ_SWITCH
config HAVE_XTENSA_GPIO32
def_bool n
-config MAY_HAVE_SMP
- def_bool n
-
menu "Processor type and features"
choice
@@ -100,7 +95,6 @@ config XTENSA_VARIANT_DC233C
config XTENSA_VARIANT_CUSTOM
bool "Custom Xtensa processor configuration"
- select MAY_HAVE_SMP
select HAVE_XTENSA_GPIO32
help
Select this variant to use a custom Xtensa processor configuration.
@@ -126,6 +120,7 @@ config XTENSA_VARIANT_MMU
bool "Core variant has a Full MMU (TLB, Pages, Protection, etc)"
depends on XTENSA_VARIANT_CUSTOM
default y
+ select MMU
help
Build a Conventional Kernel with full MMU support,
ie: it supports a TLB with auto-loading, page protection.
@@ -143,7 +138,7 @@ source "kernel/Kconfig.preempt"
config HAVE_SMP
bool "System Supports SMP (MX)"
- depends on MAY_HAVE_SMP
+ depends on XTENSA_VARIANT_CUSTOM
select XTENSA_MX
help
This option is use to indicate that the system-on-a-chip (SOC)
--
1.8.1.4
next prev parent reply other threads:[~2015-07-06 13:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 13:32 [PATCH 0/8] Support hardware perf counters on xtensa Max Filippov
2015-07-06 13:32 ` Max Filippov [this message]
2015-07-07 9:18 ` [PATCH 1/8] xtensa: clean up Kconfig dependencies for custom cores Paul Bolle
2015-07-06 13:32 ` [PATCH 2/8] xtensa: keep exception/interrupt stack continuous Max Filippov
2015-07-07 18:47 ` Chris Zankel
2015-07-07 19:46 ` Max Filippov
2015-07-07 19:47 ` Max Filippov
2015-07-06 13:32 ` [PATCH 3/8] xtensa: move oprofile stack tracing to stacktrace.c Max Filippov
2015-07-06 13:32 ` [PATCH 4/8] xtensa: select PERF_USE_VMALLOC for cache-aliasing configurations Max Filippov
2015-07-06 13:32 ` [PATCH 5/8] xtensa: add profiling IRQ type to xtensa_irq_map Max Filippov
2015-07-06 13:32 ` [PATCH 6/8] xtensa: count software page fault perf events Max Filippov
2015-07-06 13:32 ` [PATCH 7/8] xtensa: implement counting and sampling " Max Filippov
2015-07-06 13:41 ` Peter Zijlstra
2015-07-06 13:49 ` Max Filippov
2015-07-06 13:47 ` Peter Zijlstra
2015-07-06 13:56 ` Max Filippov
2015-07-06 14:05 ` Peter Zijlstra
2015-07-06 14:22 ` Max Filippov
2015-07-07 3:56 ` Chris Zankel
2015-07-06 13:32 ` [PATCH 8/8] perf tools: xtensa: add DWARF register names Max Filippov
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=1436189569-28802-2-git-send-email-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=chris@zankel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=marc@cadence.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