From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: "Olof Johansson" <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Antoine Ténart" <antoine.tenart@free-electrons.com>,
"Jimmy Xu" <zmxu@marvell.com>,
"Jisheng Zhang" <jszhang@marvell.com>,
"Alexandre Belloni" <alexandre.belloni@free-electrons.com>
Subject: [PATCH 1/2] ARM: berlin: add MACH_BERLIN_BG2Q symbol
Date: Fri, 21 Mar 2014 20:39:16 +0100 [thread overview]
Message-ID: <1395430757-8677-1-git-send-email-alexandre.belloni@free-electrons.com> (raw)
Now that we start supporting the Marvell Berlin BG2Q, add a symbol allowing to
differentiate that SoC from the other SoCs of the Berlin family.
Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
---
arch/arm/mach-berlin/Kconfig | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-berlin/Kconfig b/arch/arm/mach-berlin/Kconfig
index 7a02d222c378..0ff6f5877076 100644
--- a/arch/arm/mach-berlin/Kconfig
+++ b/arch/arm/mach-berlin/Kconfig
@@ -24,6 +24,13 @@ config MACH_BERLIN_BG2CD
select CPU_V7
select HAVE_ARM_TWD if SMP
+config MACH_BERLIN_BG2Q
+ bool "Marvell Armada 1500 Pro (BG2-Q)"
+ select CACHE_L2X0
+ select CPU_V7
+ select HAVE_ARM_TWD if SMP
+ select HAVE_SMP
+
endmenu
endif
--
1.8.3.2
next reply other threads:[~2014-03-21 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 19:39 Alexandre Belloni [this message]
2014-03-21 19:39 ` [PATCH 2/2] ARM: multi_v7_defconfig: Select CONFIG_MACH_BERLIN_BG2Q Alexandre Belloni
2014-03-21 21:43 ` Sebastian Hesselbarth
2014-04-15 19:40 ` Sebastian Hesselbarth
2014-05-05 20:55 ` Olof Johansson
2014-03-21 21:42 ` [PATCH 1/2] ARM: berlin: add MACH_BERLIN_BG2Q symbol Sebastian Hesselbarth
2014-04-22 21:24 ` Sebastian Hesselbarth
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=1395430757-8677-1-git-send-email-alexandre.belloni@free-electrons.com \
--to=alexandre.belloni@free-electrons.com \
--cc=antoine.tenart@free-electrons.com \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=zmxu@marvell.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;
as well as URLs for NNTP newsgroup(s).