From: Andrew Lunn <andrew@lunn.ch>
To: Dinh Nguyen <dinguyen@opensource.altera.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] net/phy: micrel: Follow attached_dev to get to the MAC device
Date: Sat, 17 Oct 2015 01:50:42 +0200 [thread overview]
Message-ID: <20151016235042.GA28795@lunn.ch> (raw)
In-Reply-To: <alpine.DEB.2.02.1510161749490.25648@linux-builds1>
On Fri, Oct 16, 2015 at 05:58:41PM -0500, Dinh Nguyen wrote:
> On Fri, 16 Oct 2015, Andrew Lunn wrote:
>
> > Commit "8b63ec1837fa phylib: Make PHYs children of their MDIO bus, not
> > the bus' parent." broke finding PHY properties in the MAC device tree
> > node. The parent device is now the MDIO bus, not the MAC. Use
> > attached_dev towards the MAC device tree node.
> >
> > Fixes: 8b63ec1837fa ("phylib: Make PHYs children of their MDIO bus, not the bus' parent.")
> > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > ---
> >
> > Compile tested only.
> >
> > Dinh, please could you test it and report back if it works or not.
> >
>
> This patch did not seem to fix the problem. The following code did seem to
> fix the problem:
>
> if (!of_node && dev->parent->of_node)
> - of_node = dev->parent->of_node;
> + do {
> + of_node = dev->of_node;
> + dev = dev->parent;
> + i++;
> + } while (!of_node && dev);
This might fix the issue, but it has disadvantages. As i said before,
it allows people to place phy properties into the mdio device node. We
want to be reducing placing you can add phy properties, not adding
more.
Please could you try to debug why my patch did not work. Is
attached_dev null?
Andrew
next prev parent reply other threads:[~2015-10-16 23:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 20:49 [PATCH] net/phy: micrel: Follow attached_dev to get to the MAC device Andrew Lunn
2015-10-16 22:58 ` Dinh Nguyen
2015-10-16 23:50 ` Andrew Lunn [this message]
2015-10-17 14:21 ` Dinh Nguyen
2015-10-17 15:06 ` Dinh Nguyen
2015-10-17 15:38 ` Andrew Lunn
2015-10-17 17:38 ` Florian Fainelli
2015-10-17 20:45 ` Andrew Lunn
2015-10-18 4:15 ` Dinh Nguyen
2015-10-18 5:54 ` Dinh Nguyen
2015-10-16 23:32 ` Sergei Shtylyov
2015-10-16 23:54 ` Andrew Lunn
2015-10-17 18:46 ` Sergei Shtylyov
2015-10-17 19:23 ` Sergei Shtylyov
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=20151016235042.GA28795@lunn.ch \
--to=andrew@lunn.ch \
--cc=dinguyen@opensource.altera.com \
--cc=f.fainelli@gmail.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).