From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] arm64, thunder: Add Kconfig option for Cavium Thunder SoC Family
Date: Fri, 5 Sep 2014 10:32:40 +0100 [thread overview]
Message-ID: <20140905093239.GC30401@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1409903205-2762-2-git-send-email-rric@kernel.org>
On Fri, Sep 05, 2014 at 09:46:42AM +0200, Robert Richter wrote:
> From: Radha Mohan Chintakuntla <rchintakuntla@cavium.com>
>
> Increase maximum numbers of cpus to 32. This relates to current
> maximal possible cpu number. Increasing this to 64 cpus will be a
> separate patch not part of this enablement patches.
>
> Signed-off-by: Radha Mohan Chintakuntla <rchintakuntla@cavium.com>
> Signed-off-by: Robert Richter <rrichter@cavium.com>
> ---
> arch/arm64/Kconfig | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index fd4e81a4e1ce..77fb82b0f684 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -134,6 +134,11 @@ source "kernel/Kconfig.freezer"
>
> menu "Platform selection"
>
> +config ARCH_THUNDER
> + bool "Cavium Inc. Thunder SoC Family"
> + help
> + This enables support for Cavium's Thunder Family of SoCs.
> +
> config ARCH_VEXPRESS
> bool "ARMv8 software model (Versatile Express)"
> select ARCH_REQUIRE_GPIOLIB
> @@ -256,6 +261,7 @@ config NR_CPUS
> range 2 32
> depends on SMP
> # These have to remain sorted largest to smallest
> + default "32" if ARCH_THUNDER
> default "8"
Why do you need ARCH_THUNDER? If it's just to change this default,
please don't bother - we don't do this kind of thing on x86, so why
should it be done here? Just ensure that NR_CPUS is appropriately
adjusted. Alternatively, look at how x86 deals with this (with
X86_BIGSMP / MAXSMP).
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-09-05 9:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 7:46 [PATCH v2 0/4] arm64, thunder: Enable Cavium Thunder SoC Family Robert Richter
2014-09-05 7:46 ` [PATCH v2 1/4] arm64, thunder: Add Kconfig option for " Robert Richter
2014-09-05 8:39 ` Will Deacon
2014-09-05 9:21 ` Robert Richter
2014-09-05 9:25 ` Will Deacon
2014-09-05 9:36 ` Mark Rutland
2014-09-05 10:51 ` Robert Richter
2014-09-05 9:32 ` Russell King - ARM Linux [this message]
2014-09-05 10:45 ` Robert Richter
2014-09-05 11:05 ` Russell King - ARM Linux
2014-09-05 12:51 ` Mark Rutland
2014-09-05 14:04 ` Arnd Bergmann
2014-09-05 14:22 ` Mark Rutland
2014-09-05 16:25 ` Arnd Bergmann
2014-09-08 11:01 ` Robert Richter
2014-09-08 12:29 ` Arnd Bergmann
2014-09-08 18:25 ` Rob Herring
2014-09-05 7:46 ` [PATCH v2 2/4] arm64, thunder: Add initial dts for Cavium Thunder SoC Robert Richter
2014-09-05 11:21 ` Arnd Bergmann
2014-09-11 14:51 ` Robert Richter
2014-09-05 7:46 ` [PATCH v2 3/4] arm64, thunder: Document devicetree bindings " Robert Richter
2014-09-05 8:42 ` Will Deacon
2014-09-05 9:32 ` Robert Richter
2014-09-05 9:39 ` Mark Rutland
2014-09-08 7:54 ` Robert Richter
2014-09-05 7:46 ` [PATCH v2 4/4] arm64, defconfig: Enable Cavium Thunder SoC in defconfig Robert Richter
2014-09-05 8:42 ` [PATCH v2 0/4] arm64, thunder: Enable Cavium Thunder SoC Family Will Deacon
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=20140905093239.GC30401@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).