netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Josh Cartwright <joshc@ni.com>,
	Nathan Sullivan <nathan.sullivan@ni.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Florian Fainelli <f.fainelli@gmail.com>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>
Subject: Re: [PATCH v2] net: macb: do not scan PHYs manually
Date: Fri, 29 Apr 2016 14:56:22 +0200	[thread overview]
Message-ID: <20160429125622.GE4053@lunn.ch> (raw)
In-Reply-To: <57235655.3030104@atmel.com>

> > +static int macb_mii_of_init(struct macb *bp, struct device_node *np)
> > +{
> > +	struct device_node *mdio;
> > +	int err, i;
> > +
> > +	mdio = of_get_child_by_name(np, "mdio");
> > +	if (mdio)
> > +		return of_mdiobus_register(bp->mii_bus, mdio);
> > +
> > +	dev_warn(&bp->pdev->dev,
> > +		 "using deprecated PHY probing mechanism.  Please update device tree.");
> 
> Do we need to warn here?
> 
> Too bad I was not aware of that earlier, I even updated some of my DTs
> recently with only a phy node without the "mdio" one as parents :-\

It is messy. Unfortunately, there is no binding documentation (yet)
suggesting the right way to do this. And as a result, we have
drivers/device trees doing different things, leading to workarounds
like manually scanning the bus, not listing PHYs in the device tree
and so or falling back to the old methods, etc.

We need to document how we expect this to be done, and then add
warnings in various places to encourage developers to migrate their
device trees to what has been documented.

       Andrew

  reply	other threads:[~2016-04-29 12:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 14:46 [PATCH v2] net: macb: do not scan PHYs manually Nathan Sullivan
2016-04-28 15:44 ` Nicolas Ferre
2016-04-28 15:55   ` Nathan Sullivan
2016-04-28 16:32     ` Andrew Lunn
2016-04-28 17:56       ` Nathan Sullivan
2016-04-28 18:43         ` Andrew Lunn
2016-04-28 18:55           ` Nathan Sullivan
2016-04-28 18:59             ` Andrew Lunn
2016-04-28 20:03               ` Florian Fainelli
2016-04-28 20:10                 ` Andrew Lunn
2016-04-28 21:03               ` Josh Cartwright
2016-04-28 21:23                 ` Andrew Lunn
2016-04-29  0:34                   ` Josh Cartwright
2016-04-29 12:25                     ` Josh Cartwright
2016-04-29 12:40                       ` Nicolas Ferre
2016-04-29 12:56                         ` Andrew Lunn [this message]
2016-05-02 18:36                         ` Josh Cartwright
2016-05-02 19:08                           ` Florian Fainelli
2016-05-02 19:38                             ` Josh Cartwright
2016-04-29 12:49                       ` Andrew Lunn

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=20160429125622.GE4053@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=f.fainelli@gmail.com \
    --cc=joshc@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan.sullivan@ni.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@atmel.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).