From: Scott Wood <scottwood@freescale.com>
To: Liu Po-B43644 <B43644@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
Hu Mingkai-B21284 <B21284@freescale.com>,
Fleming Andy-AFLEMING <afleming@freescale.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH v3 2/3] powerpc/85xx: Add silicon device tree for C293
Date: Wed, 31 Jul 2013 10:46:54 -0500 [thread overview]
Message-ID: <1375285614.30721.90@snotra> (raw)
In-Reply-To: <D473A0D087F4EA47A30C37E4637E25E609DB5966@039-SN2MPN1-023.039d.mgd.msft.net> (from B43644@freescale.com on Tue Jul 30 21:13:28 2013)
On 07/30/2013 09:13:28 PM, Liu Po-B43644 wrote:
>=20
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Wednesday, July 31, 2013 2:28 AM
> > To: Liu Po-B43644
> > Cc: linuxppc-dev@ozlabs.org; galak@kernel.crashing.org; Fleming =20
> Andy-
> > AFLEMING; Hu Mingkai-B21284; Liu Po-B43644
> > Subject: Re: [PATCH v3 2/3] powerpc/85xx: Add silicon device tree =20
> for
> > C293
> >
> > On 07/30/2013 03:49:22 AM, Po Liu wrote:
> > > + crypto@80000 {
> > > +/include/ "qoriq-sec6.0-0.dtsi"
> > > + };
> > > +
> > > + crypto@80000 {
> > > + reg =3D <0x80000 0x20000>;
> > > + ranges =3D <0x0 0x80000 0x20000>;
> > > +
> > > + jr@1000{
> > > + interrupts =3D <45 2 0 0>;
> > > + };
> > > + jr@2000{
> > > + interrupts =3D <57 2 0 0>;
> > > + };
> > > + };
> >
> > Do these inline the way the example shows.
> Sorry, Scott, I just remember in this way, the node can't be =20
> recognized by system when run Uboot. The include can't be in the =20
> crypto@80000. See the discussion in =20
> http://git.am.freescale.net:8181/#/c/736/ .
> Maybe I should re-modify the example file.
git.am.freescale.net is not accessible outside of Freescale; don't =20
reference it on external lists. In any case, I don't know what =20
specifically you want me to look at there. Just put the explanation =20
here.
I do not expect the dtc output to be any different between the two =20
methods. Could you check this (by using dtc to decompile the dtb =20
afterward) and point out exactly how the output differs between the two =20
approaches?
-Scott=
next prev parent reply other threads:[~2013-07-31 15:47 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 [this message]
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 ` [1/4] " Scott Wood
2013-07-23 8:01 ` 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=1375285614.30721.90@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B21284@freescale.com \
--cc=B43644@freescale.com \
--cc=afleming@freescale.com \
--cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.