From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 4/5] arm64: Add support for Spreadtrum's Sharkl64 Platform in Kconfig and defconfig
Date: Fri, 16 Jan 2015 10:48:42 +0000 [thread overview]
Message-ID: <20150116104842.GE21809@leverpostej> (raw)
In-Reply-To: <1421402411-3479-5-git-send-email-chunyan.zhang@spreadtrum.com>
On Fri, Jan 16, 2015 at 10:00:10AM +0000, Chunyan Zhang wrote:
> From: Zhizhou Zhang <zhizhou.zhang@spreadtrum.com>
>
> Adds support for Spreadtrum's SoC Platform in the arm64 Kconfig and
> defconfig files.
>
> Signed-off-by: Zhizhou Zhang <zhizhou.zhang@spreadtrum.com>
> Signed-off-by: Orson Zhai <orson.zhai@spreadtrum.com>
> Signed-off-by: Chunyan Zhang <chunyan.zhang@spreadtrum.com>
> ---
> arch/arm64/Kconfig | 5 +++++
> arch/arm64/configs/defconfig | 1 +
> 2 files changed, 6 insertions(+)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index b1f9a20..885c1f4 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -153,6 +153,11 @@ config ARCH_SEATTLE
> help
> This enables support for AMD Seattle SOC Family
>
> +config ARCH_SPRD
This should presumably be ARCH_SHARKL64, so you can add other SoC
families later. The other entries in here are already formatted that
way.
I wonder if we should have these of the form ARCH_${VENDOR}_${FAMILY}
(e.g. ARCH_SPRD_SHARKL64) rather than just ARCH_${FAMILY} to save
ourselves from name conflicts in future (and to make it easier to grep
for a particular vendor's config options).
> + bool "Spreadtrum SoC platform"
bool "Spreadtrun Sharkl64 SoC Family"
> + help
> + Support for Spreadtrum ARM based SoCs
Support for the Spreadtrum Sharkl64 SoC family.
Thanks,
Mark.
> +
> config ARCH_THUNDER
> bool "Cavium Inc. Thunder SoC Family"
> help
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index dd301be..c1677ca 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -33,6 +33,7 @@ CONFIG_MODULE_UNLOAD=y
> # CONFIG_BLK_DEV_BSG is not set
> # CONFIG_IOSCHED_DEADLINE is not set
> CONFIG_ARCH_THUNDER=y
> +CONFIG_ARCH_SPRD=y
> CONFIG_ARCH_VEXPRESS=y
> CONFIG_ARCH_XGENE=y
> CONFIG_PCI=y
> --
> 1.7.9.5
>
>
next prev parent reply other threads:[~2015-01-16 10:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sc9836-v5>
2015-01-16 10:00 ` [PATCH v5 0/5] Add Spreadtrum Sharkl64 Platform support Chunyan Zhang
2015-01-16 10:00 ` [PATCH v5 1/5] Documentation: DT: Renamed of-serial.txt to 8250.txt Chunyan Zhang
2015-01-16 14:11 ` Rob Herring
2015-01-16 10:00 ` [PATCH v5 2/5] Documentation: DT: Add bindings for Spreadtrum SoC Platform Chunyan Zhang
2015-01-16 10:21 ` Mark Rutland
2015-01-16 12:53 ` Lyra Zhang
2015-01-16 14:11 ` Mark Rutland
2015-01-17 8:10 ` Orson Zhai
2015-01-16 10:00 ` [PATCH v5 3/5] arm64: dts: Add support for Spreadtrum SC9836 SoC in dts and Makefile Chunyan Zhang
2015-01-16 10:35 ` Mark Rutland
2015-01-16 12:49 ` Orson Zhai
2015-01-16 14:09 ` Mark Rutland
2015-01-17 8:47 ` Orson Zhai
2015-01-16 10:00 ` [PATCH v5 4/5] arm64: Add support for Spreadtrum's Sharkl64 Platform in Kconfig and defconfig Chunyan Zhang
2015-01-16 10:48 ` Mark Rutland [this message]
2015-01-16 11:50 ` Lyra Zhang
2015-01-16 10:00 ` [PATCH v5 5/5] tty/serial: Add Spreadtrum sc9836-uart driver support Chunyan Zhang
2015-01-16 10:26 ` Arnd Bergmann
2015-01-16 11:02 ` Baruch Siach
2015-01-16 15:20 ` Peter Hurley
2015-01-20 12:11 ` Orson Zhai
2015-01-20 13:39 ` Peter Hurley
2015-01-16 16:41 ` Rob Herring
2015-01-19 9:55 ` Lyra Zhang
2015-01-19 14:11 ` Rob Herring
2015-01-20 7:37 ` Lyra Zhang
2015-01-20 8:41 ` Orson Zhai
2015-01-20 20:17 ` Rob Herring
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=20150116104842.GE21809@leverpostej \
--to=mark.rutland@arm.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).