linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/9] ARM: hisi: enable Hi3519 soc
Date: Thu, 03 Dec 2015 10:40:01 +0100	[thread overview]
Message-ID: <8647404.sBOFNLAMdU@wuerfel> (raw)
In-Reply-To: <1449110565-23590-1-git-send-email-xuejiancheng@huawei.com>

On Thursday 03 December 2015 10:42:45 Jiancheng Xue wrote:
> --- a/arch/arm/mach-hisi/Kconfig
> +++ b/arch/arm/mach-hisi/Kconfig
> @@ -12,6 +12,14 @@ if ARCH_HISI
>  
>  menu "Hisilicon platform type"
>  
> +config ARCH_HI3519
> +       bool "Hisilicon Hi3519 Soc" if ARCH_MULTI_V7
> +       select HAVE_ARM_ARCH_TIMER
> +       select ARCH_HAS_RESET_CONTROLLER
> +
> +       help
> +         Support for Hisilicon Hi3519 Soc
> +
>  config ARCH_HI3xxx
>         bool "Hisilicon Hi36xx family" if ARCH_MULTI_V7
>         select CACHE_L2X0

Do those need to be separate? I would just extend the Hi36xx
to cover all Hi3xxx, if nothing in the platform code really
depends on this.

> +
> +static const char *const hi3519_compat[] __initconst = {
> +       "hisilicon,hi3519",
> +       NULL,
> +};
> +
> +DT_MACHINE_START(HI3519_DT, "Hisilicon Hi3519 (Flattened Device Tree)")
> +       .dt_compat      = hi3519_compat,
> +MACHINE_END

Also drop the "(Flattened Device Tree)" part of the name, we don't
support any other kind anyway.

	Arnd

  reply	other threads:[~2015-12-03  9:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03  2:42 [PATCH v2 3/9] ARM: hisi: enable Hi3519 soc Jiancheng Xue
2015-12-03  9:40 ` Arnd Bergmann [this message]
2015-12-04  4:07   ` xuejiancheng
2015-12-04 21:54     ` Arnd Bergmann
2015-12-07  6:58       ` xuejiancheng
2015-12-07  9:46         ` Arnd Bergmann
2015-12-08  1:55           ` xuejiancheng
2015-12-08  3:03             ` xuejiancheng
2015-12-09 15:32               ` Arnd Bergmann
2015-12-10  6:13                 ` xuejiancheng
2015-12-10  8:25                   ` Arnd Bergmann

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=8647404.sBOFNLAMdU@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;
as well as URLs for NNTP newsgroup(s).