From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: PRIMA2: make mach-prima2 common for all SiRF series SoC
Date: Mon, 20 Aug 2012 21:06:42 +0000 [thread overview]
Message-ID: <201208202106.43206.arnd@arndb.de> (raw)
In-Reply-To: <1345450787-17246-3-git-send-email-Barry.Song@csr.com>
On Monday 20 August 2012, Barry Song wrote:
> From: Barry Song <Baohua.Song@csr.com>
>
> We will have SiRF Marco and Polo, so rename the dir to mach-sirf
> and add Kconfig menu
>
> Signed-off-by: Baohua Song <Baohua.Song@csr.com>
> ---
> arch/arm/Kconfig | 10 +++++-----
> arch/arm/Makefile | 2 +-
> arch/arm/mach-sirf/Kconfig | 16 ++++++++++++++++
> arch/arm/{mach-prima2 => mach-sirf}/Makefile | 0
> arch/arm/{mach-prima2 => mach-sirf}/Makefile.boot | 0
> .../arm/{mach-prima2 => mach-sirf}/board-generic.c | 0
> arch/arm/{mach-prima2 => mach-sirf}/common.h | 0
> .../include/mach/clkdev.h | 0
> .../include/mach/debug-macro.S | 0
> .../include/mach/entry-macro.S | 0
> .../{mach-prima2 => mach-sirf}/include/mach/gpio.h | 0
> .../include/mach/hardware.h | 0
> .../{mach-prima2 => mach-sirf}/include/mach/irqs.h | 0
> .../{mach-prima2 => mach-sirf}/include/mach/map.h | 0
I'm not sure if we should rename all of these right now. I've been thinking
about moving all of recent and simple ARMv7 based platforms (socfpga, zynq,
prima2, ...) into a single directory, where they would basically end up
being one file per platform. We should discuss this at the ARM mini summit,
and I can let you know the outcome of it. I don't object on the rename in
principle, but it might end up causing extra churn.
> +if ARCH_SIRF
> +
> +choice
> + prompt "Qualcomm SiRF SoC Type"
> + default ARCH_PRIMA2
I'm curious about this: I did read that Samsung acquired CSR, and
you list the chips as Qualcomm. What's the story here?
> +config ARCH_PRIMA2
> + bool "CSR SiRFSoC PRIMA2 ARM Cortex A9 Platform"
> + select CPU_V7
> + select ZONE_DMA
> + help
> + Support for CSR SiRFSoC ARM Cortex A9 Platform
> +
> +endchoice
Is this still needed? When you add other SoC type here, would you
build kernels that are for just one of them in practice? If they
are completely generic anyway, you can skip the submenu.
Arnd
next prev parent reply other threads:[~2012-08-20 21:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 8:19 [PATCH 0/3] ARM: PRIMA2: some patches prepared to support new SiRF SoCs Barry Song
2012-08-20 8:19 ` [PATCH 1/3] ARM: PRIMA2: use DT_MACHINE_START and convert to generic board Barry Song
2012-08-20 20:56 ` Arnd Bergmann
2012-08-21 1:49 ` Barry Song
2012-08-21 7:53 ` Arnd Bergmann
2012-08-21 8:26 ` Barry Song
2012-08-21 8:44 ` Arnd Bergmann
2012-08-20 8:19 ` [PATCH 2/3] ARM: PRIMA2: make mach-prima2 common for all SiRF series SoC Barry Song
2012-08-20 21:06 ` Arnd Bergmann [this message]
2012-08-21 1:56 ` Barry Song
2012-08-21 7:57 ` Arnd Bergmann
2012-08-21 9:16 ` Barry Song
2012-08-21 9:20 ` Arnd Bergmann
2012-08-28 6:15 ` Barry Song
2012-08-28 8:08 ` Barry Song
2012-08-28 14:28 ` Stephen Warren
2012-08-28 14:57 ` Barry Song
2012-08-21 9:29 ` Barry Song
2012-08-21 10:16 ` Arnd Bergmann
2012-08-21 2:06 ` Barry Song
2012-08-21 7:55 ` Arnd Bergmann
2012-08-20 8:19 ` [PATCH 3/3] ARM: SIRF: make sirf irqchip driver selectable since new SoCs will have GIC Barry Song
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=201208202106.43206.arnd@arndb.de \
--to=arnd@arndb.de \
--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).