From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 6/8] ARM: hisi: add hip04 SoC support
Date: Fri, 04 Apr 2014 17:43:41 +0200 [thread overview]
Message-ID: <8340307.jkTP7h04Ur@wuerfel> (raw)
In-Reply-To: <7hd2gxywf3.fsf@paris.lan>
On Friday 04 April 2014 07:57:36 Kevin Hilman wrote:
> Haojian Zhuang <haojian.zhuang@linaro.org> writes:
>
> > Hisilicon Hi3xxx is based on Cortex A9 Core. Now HiP04 SoC is based on
> > Cortex A15 Core. And HiP04 supports LPAE to support large memory.
> >
> > Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
>
> [...]
>
> > diff --git a/arch/arm/mach-hisi/Kconfig b/arch/arm/mach-hisi/Kconfig
> > index da16efd..707abfe 100644
> > --- a/arch/arm/mach-hisi/Kconfig
> > +++ b/arch/arm/mach-hisi/Kconfig
> > @@ -19,6 +19,16 @@ config ARCH_HI3xxx
> > help
> > Support for Hisilicon Hi36xx/Hi37xx processor family
> >
> > +config ARCH_HIP04
> > + bool "Hisilicon HiP04 Cortex A15 family" if ARCH_MULTI_V7
> > + select ARM_LPAE
>
> Presumably this SoC can support non-LPAE also, correct? If so, LPAE
> should't be selected here, or else it will force LPAE on in a multi_v7
> build also.
Actually even if it doesn't support non-LPAE, using "select" is still
wrong for the same reason.
I think we should actually extend the CPU selection phase for multiplatform,
so we have separate symbols for ARCH_MULTI_V7 (non-LPAE) and
ARCH_MULTI_V7_LPAE. These would still be selectable at the same time,
but you should only be able to turn on CONFIG_LPAE if ARCH_MULTI_V7
is disabled.
A platform that cannot run without LPAE conversely would have to depend
on (ARCH_MULTI_V7_LPAE && !ARCH_MULTI_V7 && !ARCH_MULTI_V6). Once it
does this, it can 'select LPAE' without breaking other platforms.
Arnd
next prev parent reply other threads:[~2014-04-04 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 8:03 [PATCH v1 0/8] support Hisilicon HiP04 Haojian Zhuang
2014-04-01 8:03 ` [PATCH v1 1/8] ARM: debug: add HiP04 debug uart Haojian Zhuang
2014-04-01 8:03 ` [PATCH v1 2/8] ARM: hisi: add ARCH_HISI Haojian Zhuang
2014-04-01 8:03 ` [PATCH v1 3/8] irq: gic: use mask field in GICC_IAR Haojian Zhuang
2014-04-01 8:03 ` [PATCH v1 4/8] irq: gic: extends the cpu interface to 16 Haojian Zhuang
2014-04-01 8:03 ` [PATCH v1 5/8] ARM: mcpm: change max clusters to 4 Haojian Zhuang
2014-04-01 8:03 ` [PATCH v1 6/8] ARM: hisi: add hip04 SoC support Haojian Zhuang
2014-04-04 14:57 ` Kevin Hilman
2014-04-04 15:43 ` Arnd Bergmann [this message]
2014-04-06 2:01 ` Olof Johansson
2014-04-06 18:27 ` Arnd Bergmann
2014-04-01 8:03 ` [PATCH v1 7/8] ARM: dts: add hip04-d01 dts file Haojian Zhuang
2014-04-01 8:03 ` [PATCH v1 8/8] ARM: config: append hip04_defconfig Haojian Zhuang
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=8340307.jkTP7h04Ur@wuerfel \
--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