[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56693EE2.20501@huawei.com>
Date: Thu, 10 Dec 2015 16:59:14 +0800
From: xuejiancheng <xuejiancheng@...wei.com>
To: Arnd Bergmann <arnd@...db.de>
CC: <linux-arm-kernel@...ts.infradead.org>, <robh+dt@...nel.org>,
<pawel.moll@....com>, <mark.rutland@....com>,
<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
<linux@....linux.org.uk>, <khilman@...aro.org>, <olof@...om.net>,
<xuwei5@...ilicon.com>, <haojian.zhuang@...aro.org>,
<zhangfei.gao@...aro.org>, <bintian.wang@...wei.com>,
<suwenping@...ilicon.com>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <yanhaifeng@...ilicon.com>,
<gaofei@...ilicon.com>, <ml.yang@...ilicon.com>,
<yanghongwei@...ilicon.com>
Subject: Re: [PATCH v2 4/9] ARM: dts: add dts files for hi3519-demb board
On 2015/12/10 16:04, Arnd Bergmann wrote:
> On Thursday 10 December 2015 14:32:05 xuejiancheng wrote:
>>>
>>> This is not what I meant. You have to use "syscon" as the most generic
>>> "compatible" value here, but should add a machine specific string
>>> as a more specific one. "hisilicon,sysctrl" is not appropriate because
>>> it does not identify the IP block uniquely, you can only use that
>>> in combination with another more specific string.
>>
>> OK. I will use "hisilicon,hi3519-syscon" and "syscon" as the compatible value
>> for the sysctrl node in hi3519.dtsi.
>>
>
> Why hisilicon,hi3519-syscon instead of hisilicon,hi3519-sysctrl?
> Is this not called a sysctrl at all in the datasheet then?
It is OK to use hisilicon,hi3519-sysctrl.
I thought syscon was more commonly used as abbr. of system-controller in the kernel code.
> Arnd
>
> .
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists