From: Scott Wood <scottwood@freescale.com>
To: Poonam Aggrwal <poonam.aggrwal@freescale.com>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Device Tree bindings for DSP clusters and DSP CPUs
Date: Thu, 22 Aug 2013 16:44:53 -0500 [thread overview]
Message-ID: <1377207893.20722.14.camel@snotra.buserror.net> (raw)
In-Reply-To: <1377077149-24347-1-git-send-email-poonam.aggrwal@freescale.com>
On Wed, 2013-08-21 at 14:55 +0530, Poonam Aggrwal wrote:
> Binding for DSP CPU clusters and DSP CPUs for Freescale SOCs which
> have DSP CPUs in addition to PowerPC CPUs. For example B4860.
>
> Signed-off-by: Poonam Aggrwal <poonam.aggrwal@freescale.com>
> ---
> .../devicetree/bindings/powerpc/fsl/dsp-cpus.txt | 78 ++++++++++++++++++++
> 1 files changed, 78 insertions(+), 0 deletions(-)
> 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..da7f5d4
> --- /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,dsp-cluster" or "fsl,sc3900-cluster".
> +- reg : should contain the cluster index
> +
> +Required properties for DSP CPU:
> +- compatible : should be "fsl,dsp" or "fsl,sc3900".
> +- reg : should contain index of DSP CPU within the DSP clsuter.
s/clsuter/cluster/
Could you elaborate on "index of DSP CPU within the DSP cluster"? From
the examples it looks like the reg values are unique even across
clusters.
I wonder whether we should be describing this at all in the device tree
given that the topology is discoverable in registers... though that
applies to the PowerPC CPUs as well. :-)
-Scott
next parent reply other threads:[~2013-08-22 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1377077149-24347-1-git-send-email-poonam.aggrwal@freescale.com>
2013-08-22 21:44 ` Scott Wood [this message]
2013-08-21 9:20 [PATCH] Device Tree bindings for DSP clusters and DSP CPUs Poonam Aggrwal
[not found] ` <1377076830-24223-1-git-send-email-poonam.aggrwal-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-09-30 13:36 ` Aggrwal Poonam-B10812
[not found] ` <ACB6D0C0104CFF42A45A5D82A0DD4F3D1522E0F0-RL0Hj/+nBVDYdknt8GnhQq4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2013-09-30 17:07 ` Mark Rutland
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=1377207893.20722.14.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=poonam.aggrwal@freescale.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).