From: Shawn Guo <shawnguo@kernel.org>
To: Madalin-Cristian Bucur <madalin.bucur@nxp.com>
Cc: Roy Pledge <roy.pledge@nxp.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] dts: arm64: add LS1043A DPAA support
Date: Mon, 27 Mar 2017 14:27:21 +0800 [thread overview]
Message-ID: <20170327062719.GQ30608@dragon> (raw)
In-Reply-To: <HE1PR04MB11297D944241012F44C0ADF8EC3C0@HE1PR04MB1129.eurprd04.prod.outlook.com>
On Wed, Mar 22, 2017 at 10:58:12AM +0000, Madalin-Cristian Bucur wrote:
> > > +&soc {
> > > +
> > > +/include/ "qoriq-fman3-0.dtsi"
> > > +/include/ "qoriq-fman3-0-1g-0.dtsi"
> > > +/include/ "qoriq-fman3-0-1g-1.dtsi"
> > > +/include/ "qoriq-fman3-0-1g-2.dtsi"
> > > +/include/ "qoriq-fman3-0-1g-3.dtsi"
> > > +/include/ "qoriq-fman3-0-1g-4.dtsi"
> > > +/include/ "qoriq-fman3-0-1g-5.dtsi"
> > > +/include/ "qoriq-fman3-0-10g-0.dtsi"
> >
> > We usually put the includes at the beginning of the file, and #include
> > is more recommended than /include/.
>
> I'm not making use of the header file inclusion feature #include provides
> (nor plan to) in these files thus I've selected /include/ here.
Let's be simple and consistent. Use #include please.
> > > + fman@1a00000 {
> > > + enet0: ethernet@e0000 {
> > > + };
> > > +
> > > + enet1: ethernet@e2000 {
> > > + };
> > > +
> > > + enet2: ethernet@e4000 {
> > > + };
> > > +
> > > + enet3: ethernet@e6000 {
> > > + };
> > > +
> > > + enet4: ethernet@e8000 {
> > > + };
> > > +
> > > + enet5: ethernet@ea000 {
> > > + };
> > > +
> > > + enet6: ethernet@f0000 {
> > > + };
> > > + };
> >
> > I do not quite understand why these nodes are empty.
>
> These nodes provide the aliases (and custom SoC mapping) for the
> FMan ports that are used on this particular SoC. The particular
> node details are found in the port dtsi file thus no information
> is required here. Given the fact that the numbering and actual
> ports that are in use can vary between SoCs, the aliases cannot
> be included in the port dtsi nor in the FMan dtsi.
Do not completely follow. What do you mean by 'port dtsi file'? Maybe
I should wait for you new patches with better commit log and comments to
understand these odd empty nodes.
>
> > > +};
> > > diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1043a-qds.dts
> > b/arch/arm64/boot/dts/freescale/fsl-ls1043a-qds.dts
> > > index 0989d63..ee66bb2 100644
> > > --- a/arch/arm64/boot/dts/freescale/fsl-ls1043a-qds.dts
> > > +++ b/arch/arm64/boot/dts/freescale/fsl-ls1043a-qds.dts
> > > @@ -181,3 +181,5 @@
> > > reg = <0>;
> > > };
> > > };
> > > +
> > > +/include/ "fsl-ls1043-post.dtsi"
> >
> > Move it to header of the file.
>
> This is to be included at the end, to make sure the references are
> met and to allow overrides if needed.
What is broken if you move the include to header?
>
> > > diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb.dts
> > b/arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb.dts
> > > index c37110b..d94f003 100644
> > > --- a/arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb.dts
> > > +++ b/arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb.dts
> > > @@ -139,3 +139,78 @@
> > > &duart1 {
> > > status = "okay";
> > > };
> > > +
> > > +/include/ "fsl-ls1043-post.dtsi"
> > > +
> >
> > Ditto
> >
> > > +&soc {
> > > + fman@1a00000 {
> > > + ethernet@e0000 {
> >
> > You defined enet0 label. Why don't you use it?
> >
>
> The enet0 label is used by u-boot for fix-ups, providing the
> actual offset here makes it easier to follow.
You will not need to construct the node hierarchy with label. And
alias/label name is more easier to follow than offset.
Shawn
next prev parent reply other threads:[~2017-03-27 6:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 15:35 [PATCH v2 0/2] dts: arm64: add DPAA 1 support for ARM based SoCs Madalin Bucur
2017-03-01 15:35 ` [PATCH v2 1/2] dts: arm64: add LS1043A DPAA support Madalin Bucur
2017-03-14 7:07 ` Shawn Guo
2017-03-22 10:58 ` Madalin-Cristian Bucur
2017-03-27 6:27 ` Shawn Guo [this message]
2017-03-27 7:03 ` Madalin-Cristian Bucur
2017-03-27 7:55 ` Shawn Guo
2017-03-27 8:11 ` Madalin-Cristian Bucur
2017-03-27 8:55 ` Shawn Guo
2017-03-01 15:35 ` [PATCH v2 2/2] dts: arm64: add LS1046A " Madalin Bucur
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=20170327062719.GQ30608@dragon \
--to=shawnguo@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=madalin.bucur@nxp.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=roy.pledge@nxp.com \
--cc=will.deacon@arm.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