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 13:55:15 -0500 (EST) [thread overview]
Message-ID: <20160217.135515.2062303835595535344.davem@davemloft.net> (raw)
In-Reply-To: <CA+aJhH13H87z4=SBvZaOjND3RZRDSyxBp1ctYD5ssHKHg5eToQ@mail.gmail.com>
From: Nathan Rossi <nathan@nathanrossi.com>
Date: Thu, 18 Feb 2016 04:44:35 +1000
> On Thu, Feb 18, 2016 at 3:14 AM, David Miller <davem@davemloft.net> wrote:
>> 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().
>
> I am not quite sure how to handle that in a way such as to also allow
> for the probe deferral in the event that the phydev/mdio bus which the
> phy-handle points at is not yet probed itself. But I guess the real
> question is whether or not to handle the deferral at all?
I think we need some experts in this area to chime in on this issue.
prev parent reply other threads:[~2016-02-17 18:55 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
2016-02-17 18:44 ` Nathan Rossi
2016-02-17 18:55 ` David Miller [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=20160217.135515.2062303835595535344.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).