From: Scott Wood <scottwood@freescale.com>
To: Po Liu <po.liu@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Mingkai Hu <Mingkai.Hu@freescale.com>
Subject: Re: [1/4] powerpc/85xx: Add SEC6.0 device tree
Date: Mon, 22 Jul 2013 17:41:10 -0500 [thread overview]
Message-ID: <20130722224110.GA26221@home.buserror.net> (raw)
In-Reply-To: <1366854857-22791-1-git-send-email-Po.Liu@freescale.com>
On Thu, Apr 25, 2013 at 09:54:14AM +0800, Po Liu wrote:
> From: Mingkai Hu <Mingkai.Hu@freescale.com>
>
> Add device tree for SEC 6.0 used on C29x silicon.
>
> Signed-off-by: Mingkai Hu <Mingkai.Hu@freescale.com>
> Singed-off-by: Po Liu <Po.Liu@freescale.com>
I've heard of patches being flamed, but here we want signing, not
singeing. :-)
Don't forget that you can use the -s option to have git add the signoff
for you.
> ---
> Base on git://git.am.freescale.net/gitolite/mirrors/linux-2.6.git
This URL is not accessible outside Freescale, so don't reference it when
posting patches publicly.
If your patch is against the latest upstream code, you don't need to say
anything special about that. You only need to make a note when it's
against some other yet-to-be-merged tree or patch.
> + compatible = "fsl,sec-v6.0", "fsl,sec-v5.2",
> + "fsl,sec-v5.0", "fsl,sec-v4.4",
> + "fsl,sec-v4.0";
> + fsl,sec-era = <6>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + jr@1000 {
> + compatible = "fsl,sec-v6.0-job-ring",
> + "fsl,sec-v5.2-job-ring",
> + "fsl,sec-v5.0-job-ring",
> + "fsl,sec-v4.4-job-ring",
> + "fsl,sec-v4.0-job-ring";
> + reg = <0x1000 0x1000>;
> + };
> +
> + jr@2000 {
> + compatible = "fsl,sec-v6.0-job-ring",
> + "fsl,sec-v5.2-job-ring",
> + "fsl,sec-v5.0-job-ring",
> + "fsl,sec-v4.4-job-ring",
> + "fsl,sec-v4.0-job-ring";
> + reg = <0x2000 0x1000>;
> + };
You claim compatibility with a bunch of prior SECs, but sec-v5.2 has four
job rings and an rtic node. Likewise for the previous compatibles
listed. This has two job rings and no rtic.
Can you point to where in the SEC v4.0 binding (I don't see a binding for
the subsequent versions), it says that these are optional?
-Scott
next prev parent reply other threads:[~2013-07-22 22:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 1:54 [PATCH 1/4] powerpc/85xx: Add SEC6.0 device tree Po Liu
2013-04-25 1:54 ` [PATCH 2/4] powerpc/85xx: Add silicon device tree for C293 Po Liu
2013-04-25 1:54 ` [PATCH 3/4] powerpc/85xx: Add C293PCIE board support Po Liu
2013-07-22 22:58 ` [3/4] " Scott Wood
2013-07-23 7:47 ` Liu Po-B43644
2013-07-23 16:22 ` Scott Wood
2013-04-25 1:54 ` [PATCH 4/4] powerpc/85xx: Update mpc85xx_defconfig for C293PCIE Po Liu
2013-07-22 22:59 ` [4/4] " Scott Wood
2013-07-22 23:00 ` Scott Wood
2013-07-23 7:13 ` Liu Po-B43644
2013-07-26 2:41 ` [PATCH v2 1/3] powerpc/85xx: Add SEC6.0 device tree Po Liu
2013-07-26 2:41 ` [PATCH v2 2/3] powerpc/85xx: Add silicon device tree for C293 Po Liu
2013-07-26 2:41 ` [PATCH v2 3/3] powerpc/85xx: Add C293PCIE board support Po Liu
2013-07-26 21:59 ` Scott Wood
2013-07-29 2:20 ` Liu Po-B43644
2013-07-29 18:10 ` Scott Wood
2013-07-30 8:49 ` [PATCH v3 1/3] powerpc/85xx: Add SEC6.0 device tree Po Liu
2013-07-30 8:49 ` [PATCH v3 2/3] powerpc/85xx: Add silicon device tree for C293 Po Liu
2013-07-30 18:28 ` Scott Wood
2013-07-31 2:13 ` Liu Po-B43644
2013-07-31 15:46 ` Scott Wood
2013-08-01 2:32 ` Liu Po-B43644
2013-08-07 23:24 ` Scott Wood
2013-07-30 8:49 ` [PATCH v3 3/3] powerpc/85xx: Add C293PCIE board support Po Liu
2013-07-30 18:29 ` Scott Wood
2013-08-02 6:39 ` [PATCH v4 1/3] powerpc/85xx: Add SEC6.0 device tree Po Liu
2013-08-02 6:39 ` [PATCH v4 2/3] powerpc/85xx: Add silicon device tree for C293 Po Liu
2013-08-02 6:39 ` [PATCH v4 3/3] powerpc/85xx: Add C293PCIE board support Po Liu
2013-07-26 21:55 ` [PATCH v2 1/3] powerpc/85xx: Add SEC6.0 device tree Scott Wood
2013-07-29 2:14 ` Liu Po-B43644
2013-07-22 22:41 ` Scott Wood [this message]
2013-07-23 8:01 ` [1/4] " Liu Po-B43644
2013-07-23 23:24 ` 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=20130722224110.GA26221@home.buserror.net \
--to=scottwood@freescale.com \
--cc=Mingkai.Hu@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=po.liu@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).