From: Scott Wood <oss@buserror.net>
To: Ashish kumar <Ashish.kumar@nxp.com>
Cc: scott.wood@nxp.com, linuxppc-dev@lists.ozlabs.org,
Shaveta Leekha <Shaveta.Leekha@nxp.com>
Subject: Re: arch/PPC:B4860qds/B4420qds: Updates to device trees for B4860 for DSP clusters and their L2 caches
Date: Tue, 8 Mar 2016 17:57:49 -0600 [thread overview]
Message-ID: <20160308235749.GA1048@home.buserror.net> (raw)
In-Reply-To: <1453987059-26263-1-git-send-email-Ashish.Kumar@nxp.com>
On Thu, Jan 28, 2016 at 06:47:39PM +0530, Ashish kumar wrote:
> B4860 has 1 PPC core cluster and 3 DSP core clusters.
> Similarly B4420 has 1 PPC core cluster and 1 DSP core cluster.
>
> Each DSP core cluster consists of 2 SC3900 cores and a shared L2 cache.
>
> Add DSP clusters for B4420
> The L2 cache nodes such that they now appear in only the
> soc specific dtsi files(b4860si-post.dtsi and b4420si-post.dtsi).
>
> Signed-off-by: Ashish Kumar <Ashish.Kumar@nxp.com>
> Signed-off-by: Shaveta Leekha <Shaveta.Leekha@nxp.com>
The subject line is way too long, and has a non-standard prefix.
It should be something like "powerpc/fsl: Add DSP clusters and their L2 nodes"
> +
> + dsp-clusters {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + dsp-cluster0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "fsl,sc3900-cluster";
> + reg = <0>;
> +
> + dsp0: dsp@0 {
> + compatible = "fsl,sc3900";
> + reg = <0>;
> + next-level-cache = <&L2_2>;
> + };
> + dsp1: dsp@1 {
> + compatible = "fsl,sc3900";
> + reg = <1>;
> + next-level-cache = <&L2_2>;
> + };
> + };
> + };
Where is the binding for this stuff?
Why "dsp-cluster0" instead of "dsp-cluster@0"?
-Scott
prev parent reply other threads:[~2016-03-08 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 13:17 [PATCH] arch/PPC:B4860qds/B4420qds: Updates to device trees for B4860 for DSP clusters and their L2 caches Ashish Kumar
2016-03-08 23:57 ` Scott Wood [this message]
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=20160308235749.GA1048@home.buserror.net \
--to=oss@buserror.net \
--cc=Ashish.kumar@nxp.com \
--cc=Shaveta.Leekha@nxp.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scott.wood@nxp.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).