Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754667AbbLDENk (ORCPT ); Thu, 3 Dec 2015 23:13:40 -0500 Received: from szxga02-in.huawei.com ([119.145.14.65]:55267 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752974AbbLDENi (ORCPT ); Thu, 3 Dec 2015 23:13:38 -0500 Subject: Re: [PATCH v2 3/9] ARM: hisi: enable Hi3519 soc To: Arnd Bergmann , References: <1449110565-23590-1-git-send-email-xuejiancheng@huawei.com> <8647404.sBOFNLAMdU@wuerfel> CC: , , , , , , , , , , , , From: xuejiancheng Message-ID: <5661119E.9060309@huawei.com> Date: Fri, 4 Dec 2015 12:07:58 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <8647404.sBOFNLAMdU@wuerfel> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.217.211] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.566111AF.0008,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 8d404968a49b1028c9ea4c1df3039069 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1748 Lines: 59 Hi Arnd, On 2015/12/3 17:40, Arnd Bergmann wrote: > 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. For HI3519, there is really no special platform code. But HI35xx and HI36xx soc families belong to different product lines in hisilicon. HI35xx family also composes of various architectures socs(single core, smp and big-little). So I think it may be clear to have separate arch definitions. Could you give me more suggestions about this? Thank you! >> + >> +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. OK. > > Arnd > > . > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/