From: Wan Zongshun <vw@iommu.org>
To: Afzal Mohammed <afzal.mohd.ma@gmail.com>
Cc: devicetree@vger.kernel.org, jason@lakedaemon.net,
Arnd Bergmann <arnd@arndb.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, p.zabel@pengutronix.de,
Thomas Gleixner <tglx@linutronix.de>,
Wan Zongshun <mcuos.com@gmail.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 08/10] ARM: dts: nuc900: Add nuc970 dts files
Date: Wed, 13 Jul 2016 15:26:40 +0800 [thread overview]
Message-ID: <5785ED30.4090206@iommu.org> (raw)
In-Reply-To: <20160712153910.GA3507@afzalpc>
On 2016年07月12日 23:39, Afzal Mohammed wrote:
> Hi,
>
> On Sun, Jul 10, 2016 at 03:42:20PM +0800, Wan Zongshun wrote:
>> This patch is to add dts support for nuc970 platform.
>
> cpu ! in soc ? lost in fab ? ;)
Do you mean I should add cpus into soc like?
cpus {
#address-cells = <0>;
#size-cells = <0>;
cpu {
compatible = "arm,arm926ej-s";
device_type = "cpu";
};
};
>
> Regards
> afzal
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2016-07-13 7:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 7:42 [PATCH v2 08/10] ARM: dts: nuc900: Add nuc970 dts files Wan Zongshun
2016-07-10 7:42 ` [PATCH v2 09/10] Documentation: devicetree: Add dts description for nuc900 Wan Zongshun
2016-07-10 22:17 ` Arnd Bergmann
2016-07-11 2:13 ` Wan Zongshun
2016-07-11 7:46 ` Arnd Bergmann
2016-07-10 22:22 ` Arnd Bergmann
2016-07-10 7:42 ` [PATCH v2 10/10] nuc900: add nuc970 platform defconfig file Wan Zongshun
2016-07-12 15:39 ` [PATCH v2 08/10] ARM: dts: nuc900: Add nuc970 dts files Afzal Mohammed
2016-07-13 7:26 ` Wan Zongshun [this message]
2016-07-13 17:18 ` Afzal Mohammed
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=5785ED30.4090206@iommu.org \
--to=vw@iommu.org \
--cc=afzal.mohd.ma@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mcuos.com@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=tglx@linutronix.de \
/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).