From: Scott Wood <scottwood@freescale.com>
To: Aggrwal Poonam-B10812 <Poonam.Aggrwal@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH 2/4] powerpc/device-tree: bindings for DSP cores/clusters for Freescale SOCs
Date: Mon, 21 Sep 2015 15:01:02 -0500 [thread overview]
Message-ID: <1442865662.19102.172.camel@freescale.com> (raw)
In-Reply-To: <DM2PR0301MB07016FC9BFCEB4A2C38168AB8C460@DM2PR0301MB0701.namprd03.prod.outlook.com>
On Mon, 2015-09-21 at 03:36 -0500, Aggrwal Poonam-B10812 wrote:
>
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Sunday, September 20, 2015 5:45 AM
> > To: Aggrwal Poonam-B10812 <Poonam.Aggrwal@freescale.com>
> > Cc: linuxppc-dev@lists.ozlabs.org; linux-kernel@vger.kernel.org;
> > devicetree-
> > discuss@lists.ozlabs.org
> > Subject: Re: [PATCH 2/4] powerpc/device-tree: bindings for DSP
> > cores/clusters for Freescale SOCs
> >
> > On Sat, 2015-09-19 at 23:46 +0530, Poonam Aggrwal wrote:
> > > From: poonam aggrwal <poonam.aggrwal@freescale.com>
> > >
> > > Device Tree Bindings for DSP CPU clusters and DSP CPUs for Freescale
> > > PowerPC SOCs which have DSP CPUs in addition to PowerPC CPUs.
> > > For example B4860 has 3 DSP clusters which have 2 SC3900 cores each.
> > >
> > > Signed-off-by: Poonam Aggrwal <poonam.aggrwal@freescale.com>
> > > ---
> > > - based of:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > > branch master
> > >
> > > This patch was sent earlier and some comments were received. Some have
> > > been taken care; others we can further discuss. Apologize for not
> > > following up on them in time.
> > > .../devicetree/bindings/powerpc/fsl/dsp-cpus.txt | 78
> > > ++++++++++++++++++++++
> > > 1 file changed, 78 insertions(+)
> > > create mode 100644
> > Documentation/devicetree/bindings/powerpc/fsl/dsp-
> > > cpus.txt
> > >
> > > diff --git
> > > a/Documentation/devicetree/bindings/powerpc/fsl/dsp-cpus.txt
> > > b/Documentation/devicetree/bindings/powerpc/fsl/dsp-cpus.txt
> > > new file mode 100644
> > > index 0000000..6d901ef
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/powerpc/fsl/dsp-cpus.txt
> > > @@ -0,0 +1,78 @@
> > >
> > +=========================================================
> > ==========
> > > +Binding for DSP CPU clusters and DSP CPUs for Freescale SOCs which
> > > +have DSP CPUs in addition to PowerPC cpus.
> > > +Copyright 2013 Freescale Semiconductor Inc.
> > > +
> > > +Power Architecture CPUs in Freescale SOCs are represented in device
> > > +trees
> > > as
> > > +per the definition in ePAPR.
> > > +
> > > +Required properties for DSP CPU cluster:
> > > +- compatible : should be "fsl,sc3900-cluster".
> > > +- reg : should contain the cluster index
> > > +
> > > +Required properties for DSP CPU:
> > > +- compatible : should be "fsl,sc3900".
> > > +- reg : should contain index of DSP CPU within the DSP clsuter.
> > > +- next-level-cache : should point to the phandle of the next-level L2
> > > cache.
> >
> > Why is the dsp-clusters container only shown in the example, not the
> > binding
> > itself?
>
> I will try to add more description in the binding for cluster; And the
> structure of dsp cluster (like sub node of DSP cluster is core, etc).
> Did I get your feedback right?
No, I was complaining that the example has a "dsp-clusters" container node
and the binding itself doesn't mention it at all.
-Scott
prev parent reply other threads:[~2015-09-21 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 18:16 [PATCH 2/4] powerpc/device-tree: bindings for DSP cores/clusters for Freescale SOCs Poonam Aggrwal
2015-09-20 0:15 ` Scott Wood
2015-09-21 8:36 ` Aggrwal Poonam
2015-09-21 20:01 ` 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=1442865662.19102.172.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Poonam.Aggrwal@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--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).