From: Scott Wood <scottwood@freescale.com>
To: Jia Hongtao-B38951 <hongtao.jia@freescale.com>
Cc: "edubezval@gmail.com" <edubezval@gmail.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"rui.zhang@intel.com" <rui.zhang@intel.com>
Subject: Re: [PATCH V2] QorIQ/TMU: add TMU node to device tree for QorIQ T104x
Date: Tue, 9 Jun 2015 12:47:29 -0500 [thread overview]
Message-ID: <1433872049.2477.80.camel@freescale.com> (raw)
In-Reply-To: <BLUPR03MB149DC0A753423EB27293931E1BE0@BLUPR03MB149.namprd03.prod.outlook.com>
On Mon, 2015-06-08 at 21:19 -0500, Jia Hongtao-B38951 wrote:
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Wednesday, May 27, 2015 3:38 AM
> > To: Jia Hongtao-B38951
> > Cc: edubezval@gmail.com; linuxppc-dev@lists.ozlabs.org;
> > devicetree@vger.kernel.org; robh+dt@kernel.org; rui.zhang@intel.com
> > Subject: Re: [PATCH V2] QorIQ/TMU: add TMU node to device tree for
> > QorIQ
> > T104x
> >
> > On Tue, 2015-05-26 at 01:33 -0500, Jia Hongtao-B38951 wrote:
> > > diff --git a/arch/powerpc/boot/dts/fsl/t1040si-post.dtsi
> > > > b/arch/powerpc/boot/dts/fsl/t1040si-post.dtsi
> > > > index 15ae462..bb9f792 100644
> > > > --- a/arch/powerpc/boot/dts/fsl/t1040si-post.dtsi
> > > > +++ b/arch/powerpc/boot/dts/fsl/t1040si-post.dtsi
> > > > @@ -345,6 +345,7 @@
> > > > reg = <0xea000 0x4000>;
> > > > };
> > > >
> > > > +/include/ "qoriq-tmu-t104xsi.dtsi"
> > > > /include/ "elo3-dma-0.dtsi"
> > > > /include/ "elo3-dma-1.dtsi"
> > > > /include/ "qoriq-espi-0.dtsi"
> >
> > Why is this chip-specific enough to be called "t104xsi", but not
> > chip-
> > specific enough to just go directly into t1040si-post?
>
> T104x platform share the same calibration data.
Which t104x are you referring to that doesn't use t1040si-post.dtsi?
Plus, given the numbering scheme it's always possible that a new t104x
comes out that has little to do with existing t104x.
-Scott
next prev parent reply other threads:[~2015-06-09 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 8:17 [PATCH V2] QorIQ/TMU: add TMU node to device tree for QorIQ T104x Jia Hongtao
2015-05-26 6:33 ` Hongtao Jia
2015-05-26 19:37 ` Scott Wood
2015-06-09 2:19 ` Hongtao Jia
2015-06-09 17:47 ` Scott Wood [this message]
2015-06-10 8:56 ` Hongtao Jia
2015-06-10 18:37 ` 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=1433872049.2477.80.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=hongtao.jia@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.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).