From: Scott Wood <scottwood@freescale.com>
To: Bucur Madalin-Cristian-B32716 <madalin.bucur@freescale.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Shaohui Xie <Shaohui.Xie@freescale.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Medve Emilian-EMMEDVE1 <Emilian.Medve@freescale.com>,
Liberman Igal-B31950 <Igal.Liberman@freescale.com>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] Documentation: bindings: net: DPAA corenet binding document
Date: Wed, 3 Dec 2014 16:01:28 -0600 [thread overview]
Message-ID: <1417644088.15957.235.camel@freescale.com> (raw)
In-Reply-To: <1417561420.15957.221.camel@freescale.com>
On Tue, 2014-12-02 at 17:03 -0600, Scott Wood wrote:
> On Tue, 2014-12-02 at 06:12 -0600, Bucur Madalin-Cristian-B32716 wrote:
> > > -----Original Message-----
> > > From: Wood Scott-B07421
> > > Sent: Tuesday, December 02, 2014 6:40 AM
> > >
> > > No need for the <SoC> part. As we previously discussed, the only
> > > purpose of this node is backwards compatibility with the U-Boot MAC
> > > address fixup -- if U-Boot doesn't look for the <SoC> version, then
> > > don't complicate things.
> > >
> > > Though, I can't find where U-Boot references this node. Are you sure
> > > it's not using the ethernet%d aliases like everything else, in which
> > > case why do we need this node at all?
> > >
> > > -Scott
> > >
> >
> > The initial (Freescale SDK) binding document contained those compatibles,
> > not sure what the initial intent was for the <SoC> variants.
> >
> > The "fsl,dpaa" node is of interest to the DPAA Ethernet because it is
> > the parent of the "fsl,dpa-ethernet" nodes.
>
> I'm not interested in what the SDK binding says, or what the SDK kernel
> does. I'm interested in whether there's a U-Boot compatibility issue,
> as was previously alleged. If there isn't, then there's no need for
> fsl,dpaa *or* fsl,dpa-ethernet.
OK, I found the U-Boot fixup in question. It's not for MAC addresses,
but for marking disabled ports as disabled. It marks the dpa-ethernet
node as disabled, based on it having an fsl,fman-mac property that
points to the MAC node.
U-Boot also disables the MAC node itself, so it doesn't matter if it
doesn't find fsl,fman-mac -- except for the special case of fm1-dtsec1,
which is always kept enabled because it's used for MDIO for all ports.
Based on http://patchwork.ozlabs.org/patch/410770/ there's a separate
node for mdio, so why can't we mark the MAC disabled? Assuming that
there's no real problem in marking the fm1-dtsec1 MAC node disabled, we
can consider this to be a bug in U-Boot which can be worked around by
having the fm1-dtsec1 mac node have an fsl,fman-mac property that points
to itself. This property would only go on the fm1-dtsec1 mac node and
would only be in device trees for SoCs that are supported by U-Boots old
enough to not have had the bug be fixed.
-Scott
prev parent reply other threads:[~2014-12-03 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 10:10 [PATCH] Documentation: bindings: net: DPAA corenet binding document Madalin Bucur
2014-12-02 4:39 ` Scott Wood
2014-12-02 12:12 ` Madalin-Cristian Bucur
2014-12-02 23:03 ` Scott Wood
2014-12-03 22:01 ` Scott Wood [this message]
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=1417644088.15957.235.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Emilian.Medve@freescale.com \
--cc=Igal.Liberman@freescale.com \
--cc=Shaohui.Xie@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=netdev@vger.kernel.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 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).