mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@opensource.altera.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: David Daney <ddaney@caviumnetworks.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>, <david.daney@cavium.com>,
	<peppe.cavallaro@st.com>, <srinivas.kandagatla@gmail.com>,
	<maxime.coquelin@st.com>, <patrice.chotard@st.com>,
	<heiko@sntech.de>, <Bnetdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: SoCFPGA ethernet broken
Date: Mon, 19 Oct 2015 05:50:52 -0500	[thread overview]
Message-ID: <alpine.DEB.2.02.1510190546430.27515@linux-builds1> (raw)
In-Reply-To: <alpine.DEB.2.02.1510190521370.27515@linux-builds1>

On Mon, 19 Oct 2015, Dinh Nguyen wrote:

+CC Giuseppe Cavallaro
+CC STi and Rockchip Maintainers

This is approaching beyond my breadth of knowledge on this subject, so I just
wanted to get some further insight.

> 
> On Fri, 16 Oct 2015, Andrew Lunn wrote:
> 
> > > > Maybe we need to walk up the hierarchy.
> > > > 
> > > > Perhaps something like:
> > > > 
> > > > const struct device *dev_walker;
> > > > 
> > > > dev_walker = &phydev->dev;
> > > > do {
> > > >    of_node = dev_walker->of_node;
> > > >    dev_walker = dev_walker->parent;
> > > > } while (!of_node && dev_walker);
> > > > 
> > > 
> > > The above code seems to have fixed the issue.
> > 
> > What i don't like about this is that it allows you to put these
> > properties in the mdio device node. These are phy properties, not mdio
> > properties....
> >
> 
AFAICT, the stmmac driver is allowing for the phy node to be part of the mdio.
In the function, stmmac_init_phy(), there is a separate check of a standalone
phy_node, and the case where the phy is part of the mdio.

commit "8b63ec1837fa phylib: Make PHYs children of their MDIO bus, not
the bus' parent." is now now placing a hard requirement that the phy must be
in a separate node. For now, this is breaking SoCFPGA, but I think it may also
impact Rockchip and STi?

> > If phydev->attached_dev->dev->of_node works, that would be my
> > preference.
> >

BR,
Dinh

  reply	other threads:[~2015-10-19 10:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 19:09 Dinh Nguyen
2015-10-15 20:03 ` Florian Fainelli
2015-10-15 19:59   ` Dinh Nguyen
2015-10-15 20:25     ` Florian Fainelli
2015-10-15 20:35       ` David Daney
2015-10-15 20:49         ` Dinh Nguyen
2015-10-15 21:30           ` Florian Fainelli
2015-10-16  2:32             ` Dinh Nguyen
2015-10-16  3:31               ` Andrew Lunn
2015-10-16 14:38                 ` Dinh Nguyen
2015-10-16 15:03                   ` Andrew Lunn
2015-10-16 15:31                     ` Dinh Nguyen
2015-10-16 15:56                       ` Andrew Lunn
2015-10-16 16:47                         ` David Daney
2015-10-16 19:10                           ` Dinh Nguyen
2015-10-16 19:38                             ` Andrew Lunn
2015-10-16 20:24                               ` David Daney
2015-10-16 20:29                                 ` Andrew Lunn
2015-10-19 15:14                               ` Dinh Nguyen
2015-10-19 10:50                                 ` Dinh Nguyen [this message]
2015-10-16 18:17                         ` Florian Fainelli
2015-10-16  3:04             ` Dinh Nguyen
2015-12-03 20:48       ` Pavel Machek
2015-12-03 21:23         ` David Daney
2015-12-03 23:17           ` Dinh Nguyen
2015-12-04  1:10             ` Andrew Lunn
2015-12-04  1:50               ` Andrew Lunn
2015-12-04 11:27                 ` Dinh Nguyen
2015-12-04 14:31                   ` Andrew Lunn
2015-12-04  9:38           ` Pavel Machek

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=alpine.DEB.2.02.1510190546430.27515@linux-builds1 \
    --to=dinguyen@opensource.altera.com \
    --cc=Bnetdev@vger.kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=david.daney@cavium.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=f.fainelli@gmail.com \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.coquelin@st.com \
    --cc=patrice.chotard@st.com \
    --cc=peppe.cavallaro@st.com \
    --cc=srinivas.kandagatla@gmail.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

all inboxes | Powered by JetHome®