From: David Miller <davem@davemloft.net>
To: nathan@nathanrossi.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
nicolas.ferre@atmel.com
Subject: Re: [PATCH] net: macb: Add support for phy-handle binding
Date: Wed, 17 Feb 2016 12:14:14 -0500 (EST) [thread overview]
Message-ID: <20160217.121414.529895298809970981.davem@davemloft.net> (raw)
In-Reply-To: <1455379368-18739-1-git-send-email-nathan@nathanrossi.com>
From: Nathan Rossi <nathan@nathanrossi.com>
Date: Sun, 14 Feb 2016 02:02:48 +1000
> This patch adds support for the 'phy-handle' binding which allows for a
> system to specifically select a phy which can be attached via any MDIO
> bus available in the system.
>
> Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
> Cc: Nicolas Ferre <nicolas.ferre@atmel.com>
I don't see how this can be backwards compatible at all.
In my opinion we are way too loose about handling things like this.
Existing chips that happened to have an OF node but lack a phy-handle
property are going to be broken by that change.
I know you are now going to bombard me with all kinds of reasons why
this won't happen.
Don't bother, I'm simply not interested.
All of these special cases we use (all the DT bindings are in text
files in the kernel sources, we control all of the bootloaders, etc.)
is the most shaky foundation I've ever seen upon which to erect a
stable device probing mechanism.
I'm not applying this patch until you add an error handling path from
the of_phy_connect() call that will do the existing PHY probing sequence
by hand using phy_find_first().
next prev parent reply other threads:[~2016-02-17 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 16:02 [PATCH] net: macb: Add support for phy-handle binding Nathan Rossi
2016-02-17 17:14 ` David Miller [this message]
2016-02-17 18:44 ` Nathan Rossi
2016-02-17 18:55 ` David Miller
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=20160217.121414.529895298809970981.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@nathanrossi.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).