From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 08/10] ARM: dts: zx: add an initial dts for zx296702
Date: Sat, 14 Mar 2015 22:30:59 +0100 [thread overview]
Message-ID: <2891190.FNOpxdiSkI@wuerfel> (raw)
In-Reply-To: <1426333785-3952-9-git-send-email-jun.nie@linaro.org>
On Saturday 14 March 2015 19:49:43 Jun Nie wrote:
>
> +#include "skeleton.dtsi"
> +#include <dt-bindings/clock/zx296702-clock.h>
> +#include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> +/ {
> + aliases {
> + serial0 = &uart0;
> + serial1 = &uart1;
> + };
Move the aliases to the board specific file: other boards might not
have the same set of uarts visible to users.
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + cpu at 0 {
> + compatible = "arm,cortex-a9";
> + device_type = "cpu";
> + reg = <0>;
> + };
> +
> + cpu at 1 {
> + compatible = "arm,cortex-a9";
> + device_type = "cpu";
> + reg = <1>;
> + };
> + };
> +
No enable-method?
> + lsp1crpm: lsp1crpm at 0x09400000 {
> + compatible = "zte,zx296702-lsp1crpm";
> + reg = <0x09400000 0x1000>;
> + };
What is an lsp1crpm?
> + dwmmc0: dwmmc at 0x09408000 {
The node name should be "mmc", not "dwmmc".
> +
> + clks: topcrm at 0x09800000 {
> + compatible = "zte,zx296702-topcrm";
> + reg = <0x09800000 0x1000>;
> + #clock-cells = <1>;
> + };
> +
> + lsp0crpm: lsp0crpm at 0x0b000000 {
> + compatible = "zte,zx296702-lsp0crpm";
> + reg = <0x0b000000 0x1000>;
> + };
What is a topcrm and an lsp0crpm?
> + dwmmc1: dwmmc at 0x0b003000 {
> + compatible = "snps,dw-mshc";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0x0b003000 0x1000>;
> + interrupts = <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>;
> + fifo-depth = <32>;
> + clocks = <&clks ZX296702_SDMMC1_PCLK>,
> + <&clks ZX296702_SDMMC1_WCLK>;
> + clock-names = "biu", "ciu";
> + status = "disabled";
> + };
> +
> + aon_sysctrl: aon-sysctrl at 0xa0007000 {
> + compatible = "zte,aon-sysctrl";
> + reg = <0xa0007000 0x1000>;
> + };
> + };
This looks like it's a system controller, so the node name
should probably be "system-controller", not aon-sysctrl,
and you may want to claim compatibility with "syscon" as well.
All the nodes need to have a documented binding.
Arnd
next prev parent reply other threads:[~2015-03-14 21:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 11:49 [PATCH 00/10] ZTE platform basic support Jun Nie
2015-03-14 11:49 ` [PATCH 01/10] ARM: zx: add basic support of ZTE ZX296702 Jun Nie
2015-03-14 21:21 ` Arnd Bergmann
2015-03-14 11:49 ` [PATCH 02/10] ARM: zx: add low level debug support Jun Nie
2015-03-15 22:44 ` Matthias Brugger
2015-03-15 22:48 ` Russell King - ARM Linux
2015-03-16 2:37 ` Shawn Guo
2015-03-16 10:08 ` Arnd Bergmann
2015-03-14 11:49 ` [PATCH 03/10] MAINTAINERS: add entry for ZTE ARM architecture Jun Nie
2015-03-14 11:49 ` [PATCH 04/10] ARM: zx: add initial L2CC initialization Jun Nie
2015-03-14 21:22 ` Arnd Bergmann
2015-03-16 2:48 ` Shawn Guo
2015-03-16 3:04 ` Jisheng Zhang
2015-03-16 10:41 ` Russell King - ARM Linux
2015-03-14 11:49 ` [PATCH 05/10] ARM: zx: bring up the secondary core Jun Nie
2015-03-14 21:25 ` Arnd Bergmann
2015-03-16 7:23 ` Shawn Guo
2015-03-14 11:49 ` [PATCH 06/10] ARM: zx: add cpu hotplug support Jun Nie
2015-03-14 21:26 ` Arnd Bergmann
2015-03-14 11:49 ` [PATCH 07/10] dt/binding: Document ZTE zx296702 devicetree Jun Nie
2015-03-14 11:49 ` [PATCH 08/10] ARM: dts: zx: add an initial dts for zx296702 Jun Nie
2015-03-14 21:30 ` Arnd Bergmann [this message]
2015-03-14 11:49 ` [PATCH 09/10] ARM: zx: Add basic defconfig support to ZX296702 Jun Nie
2015-03-15 13:15 ` Shawn Guo
2015-03-14 11:49 ` [PATCH 10/10] clk: zx: add zx296702 clock support Jun Nie
2015-03-14 21:33 ` Arnd Bergmann
2015-03-16 11:33 ` Russell King - ARM Linux
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=2891190.FNOpxdiSkI@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