From: xuejiancheng@huawei.com (xuejiancheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/9] ARM: dts: add dts files for hi3519-demb board
Date: Fri, 4 Dec 2015 10:27:58 +0800 [thread overview]
Message-ID: <5660FA2E.6040601@huawei.com> (raw)
In-Reply-To: <1728470.0OiiXMcl88@wuerfel>
Hi Arnd,
Thank you very much for all your comments.
On 2015/12/3 17:36, Arnd Bergmann wrote:
> On Thursday 03 December 2015 10:44:28 Jiancheng Xue wrote:
>
>> +
>> +/dts-v1/;
>> +#include "hi3519.dtsi"
>> +
>> +/ {
>> + model = "HiSilicon HI3519 DEMO Board";
>> + compatible = "hisilicon,hi3519";
>> +
>> + chosen {
>> + bootargs = "mem=64M console=ttyAMA0,115200 early_printk \
>> +root=/dev/mtdblock2 rootfstype=jffs2 \
>> +mtdparts=hi_sfc:1M(boot),4M(kernel),11M(rootfs)";
>> + };
>
> Most of the arguments should be dropped and replaced with the respective
> DT properties in this file:
>
> mem: /memory (you have that already, but the size seems wrong)
> console: /chosen/stdout-path
> early_printk: just drop this, maybe use "earlycon")
> root: this one is fine
> rootfstype: should not be needed
> mtdparts: use nodes below the MTD device
>
This chosen node is just for debug. The real parameters will be set at boot stage.
I will drop it.
>> +
>> +#include "skeleton.dtsi"
>> +#include <dt-bindings/clock/hi3519-clock.h>
>> +/ {
>> + aliases {
>> + serial0 = &uart0;
>> + };
>
> Move this into the .dts file.
OK. Thank you.
>
>> +
>> + uart0: uart at 12100000 {
>
> rename to serial at 12100000
OK.
>
>> + dual_timer1: dual_timer at 12001000 {
>> + compatible = "arm,sp804", "arm,primecell";
>> + interrupts = <0 66 4>, <0 67 4>;
>> + reg = <0x12001000 0x1000>;
>> + clocks = <&crg HI3519_FIXED_3M>;
>> + status = "disable";
>> + };
>
> rename to timer at 12001000
OK.
>
>> + sysctrl: system-controller at 12020000 {
>> + compatible = "hisilicon,sysctrl";
>> + reg = <0x12020000 0x1000>;
>> + reboot-offset = <0x4>;
>> + };
>
> Is this one identical to the one in hip04?
>
> If not, pick a new unique compatible string
Yes. It's compatible with the one in hip04.
>
>> +
>> + crg: crg at 12010000 {
>> + compatible = "hisilicon,hi3519-crg";
>
>
> what is a "crg"? Is there a standard name for these?
The "crg" means Clock and Reset Generator. It's a block which supplies clock
and reset signals for other modules in the chip. I used "hi3519-clock"
in last version patch. Rob Herring suggested that it's better to use "hi3519-crg"
as the compatible string if it's a whole block.
what about writing like this?
crg: clock-reset-controller at 12010000 {
compatible = "hisilicon,hi3519-crg";
}
>
> Arnd
>
> .
>
Jiancheng
.
next prev parent reply other threads:[~2015-12-04 2:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 2:44 [PATCH v2 4/9] ARM: dts: add dts files for hi3519-demb board Jiancheng Xue
2015-12-03 9:36 ` Arnd Bergmann
2015-12-04 2:27 ` xuejiancheng [this message]
2015-12-04 10:49 ` Arnd Bergmann
2015-12-07 6:37 ` xuejiancheng
2015-12-08 3:28 ` zhangfei
2015-12-08 3:54 ` xuejiancheng
2015-12-09 15:31 ` Arnd Bergmann
2015-12-10 6:32 ` xuejiancheng
2015-12-10 8:04 ` Arnd Bergmann
2015-12-10 8:59 ` xuejiancheng
2015-12-10 9:13 ` 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=5660FA2E.6040601@huawei.com \
--to=xuejiancheng@huawei.com \
--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).