From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: berlin: add MACH_BERLIN_BG2Q symbol
Date: Tue, 22 Apr 2014 23:24:06 +0200 [thread overview]
Message-ID: <5356DDF6.4010308@gmail.com> (raw)
In-Reply-To: <532CB252.6010702@gmail.com>
On 03/21/2014 10:42 PM, Sebastian Hesselbarth wrote:
> On 03/21/2014 08:39 PM, Alexandre Belloni wrote:
>> 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>
>
> Applied to berlin/defconfig, Thanks!
>
>> ---
>> 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
As Rob Herring pointed out, CPU_V7 is already selected by MULTI_V7.
Also, with no agreement on how to proceed with SMP, I also dropped
HAVE_SMP for now.
Sebastian
>> endmenu
>>
>> endif
>>
>
prev parent reply other threads:[~2014-04-22 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 19:39 [PATCH 1/2] ARM: berlin: add MACH_BERLIN_BG2Q symbol Alexandre Belloni
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 [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=5356DDF6.4010308@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).