From: Joel Stanley <joel@jms.id.au>
To: Brendan Higgins <brendanhiggins@google.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
avifishman70@gmail.com, tmaimon77@gmail.com,
Rick Altherr <raltherr@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH v3 2/3] arm: dts: add Nuvoton NPCM750 device tree
Date: Wed, 6 Sep 2017 14:53:26 +0930 [thread overview]
Message-ID: <CACPK8Xc0jrnx96=BoGMwQgoT2brgc0UTNU5HMHXDeFfeToVgxA@mail.gmail.com> (raw)
In-Reply-To: <20170906003016.2159-3-brendanhiggins@google.com>
On Wed, Sep 6, 2017 at 10:00 AM, Brendan Higgins
<brendanhiggins@google.com> wrote:
> +++ b/Documentation/devicetree/bindings/arm/npcm/npcm.txt
> @@ -0,0 +1,6 @@
> +NPCM Platforms Device Tree Bindings
> +-----------------------------------
> +NPCM750 SoC
> +Required root node properties:
> + - compatible = "nuvoton,npcm750";
> +
This is minimal. I assume there will be more content added as more
support is added?
Does it need it's own directory?
> diff --git a/arch/arm/boot/dts/nuvoton-npcm750-evb.dts b/arch/arm/boot/dts/nuvoton-npcm750-evb.dts
> new file mode 100644
> index 000000000000..54df32cff21b
> --- /dev/null
> +++ b/arch/arm/boot/dts/nuvoton-npcm750-evb.dts
> +
> +/dts-v1/;
> +#include "nuvoton-npcm750.dtsi"
> +
> +/ {
> + model = "Nuvoton npcm750 Development Board (Device Tree)";
> + compatible = "nuvoton,npcm750";
> +
> + chosen {
> + stdout-path = &serial3;
> + bootargs = "earlyprintk=serial,serial3,115200";
> + };
> +
> + memory {
> + reg = <0 0x40000000>;
> + };
> +
> + cpus {
> + enable-method = "nuvoton,npcm7xx-smp";
> + };
> +
> + clk: clock-controller@f0801000 {
> + status = "okay";
> + };
> +
> + apb {
> + watchdog1: watchdog@f0009000 {
> + status = "okay";
> + };
You've already got the label for the node, is there are reason you
don't use a phandle to set the status?
&watchdog1 {
status = "okay";
};
Same with the serial nodes below.
> +
> + serial0: serial0@f0001000 {
> + status = "okay";
> + };
> +
> + serial1: serial1@f0002000 {
> + status = "okay";
> + };
> +
> + serial2: serial2@f0003000 {
> + status = "okay";
> + };
> +
> + serial3: serial3@f0004000 {
> + status = "okay";
> + };
> + };
next prev parent reply other threads:[~2017-09-06 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 0:30 [PATCH v3 0/3] arm: npcm: add basic support for Nuvoton BMCs Brendan Higgins
2017-09-06 0:30 ` [PATCH v3 1/3] " Brendan Higgins
2017-09-07 15:24 ` kbuild test robot
2017-09-07 18:01 ` kbuild test robot
2017-09-06 0:30 ` [PATCH v3 2/3] arm: dts: add Nuvoton NPCM750 device tree Brendan Higgins
2017-09-06 5:23 ` Joel Stanley [this message]
2017-09-06 8:19 ` Brendan Higgins
2017-09-06 0:30 ` [PATCH v3 3/3] MAINTAINERS: Add entry for the Nuvoton NPCM architecture Brendan Higgins
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='CACPK8Xc0jrnx96=BoGMwQgoT2brgc0UTNU5HMHXDeFfeToVgxA@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=avifishman70@gmail.com \
--cc=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=raltherr@google.com \
--cc=robh+dt@kernel.org \
--cc=tmaimon77@gmail.com \
/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).