From: Scott Wood <scottwood@freescale.com>
To: Shengzhou Liu <Shengzhou.Liu@freescale.com>
Cc: Yuantian.Tang@freescale.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/4 v2] powerpc/fsl-booke: Add device tree support for T1024/T1023 SoC
Date: Wed, 8 Apr 2015 17:43:47 -0500 [thread overview]
Message-ID: <1428533027.22867.517.camel@freescale.com> (raw)
In-Reply-To: <1428489987-31209-1-git-send-email-Shengzhou.Liu@freescale.com>
On Wed, 2015-04-08 at 18:46 +0800, Shengzhou Liu wrote:
> + clockgen: global-utilities@e1000 {
> + compatible = "fsl,t1023-clockgen", "fsl,qoriq-clockgen-2.0",
> + "fixed-clock";
> + reg = <0xe1000 0x1000>;
> + clock-output-names = "sysclk";
> + #clock-cells = <0>;
Why aren't you using qoriq-clockgen2.dtsi? Where is ranges?
We've been putting the sysclk in its own node, though even after reading
the discussion in http://patchwork.ozlabs.org/patch/274134/ and
http://patchwork.ozlabs.org/patch/290226/ I still don't know what was
wrong with the unified approach.
> + data-only@0 {
> + compatible = "fsl,qe-muram-data",
> + "fsl,cpm-muram-data";
> + reg = <0x0 0x6000>;
Whitespace.
-Scott
next prev parent reply other threads:[~2015-04-08 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 10:46 [PATCH 1/4 v2] powerpc/fsl-booke: Add device tree support for T1024/T1023 SoC Shengzhou Liu
2015-04-08 10:46 ` [PATCH 2/4 v2] powerpc/fsl-booke: Add T1024 QDS board support Shengzhou Liu
2015-04-08 10:46 ` [PATCH 3/4 v2] powerpc/fsl-booke: Add T1024 RDB " Shengzhou Liu
2015-04-08 22:52 ` Scott Wood
2015-04-09 6:20 ` Shengzhou.Liu
2015-04-08 10:46 ` [PATCH 4/4 v2] powerpc/fsl-booke: Add T1023 " Shengzhou Liu
2015-04-08 22:43 ` Scott Wood [this message]
2015-04-08 22:52 ` [PATCH 1/4 v2] powerpc/fsl-booke: Add device tree support for T1024/T1023 SoC Scott Wood
2015-04-09 6:29 ` Shengzhou.Liu
2015-04-13 21:01 ` Scott Wood
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=1428533027.22867.517.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Shengzhou.Liu@freescale.com \
--cc=Yuantian.Tang@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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).