From: David Daney <ddaney@caviumnetworks.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: David Daney <ddaney.cavm@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Robert Richter <rric@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
<netdev@vger.kernel.org>, David Daney <david.daney@cavium.com>,
<linux-kernel@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
Sunil Goutham <sgoutham@cavium.com>,
Radha Mohan Chintakuntla <rchintakuntla@cavium.com>,
"David S. Miller" <davem@davemloft.net>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] net: thunderx: Cleanup PHY probing code.
Date: Fri, 11 Mar 2016 13:57:56 -0800 [thread overview]
Message-ID: <56E33F64.2000208@caviumnetworks.com> (raw)
In-Reply-To: <20160311213516.GE19277@lunn.ch>
On 03/11/2016 01:35 PM, Andrew Lunn wrote:
[...]
> How usable is the hardware without a PHY driver?
The hardware has always in the past, still does, and probably always
will work fine without a PHY driver. Link up/down are correctly handled.
> Is a better solution
> that your write a very minimal PHY driver?
No. Nothing would be gained.
All we are trying to do, is allow for loading of 1G PHY drivers via the
-EPROBE_DEFER mechanism while continuing to allow the 10G and 40G ports
to function without a PHY driver.
Specifically, we are *not* attempting to solve the problem of
re-architecting the kernel phy_device infrastructure so that it would be
possible to write a Cortina PHYs driver. Nor are we proposing that a
Cortina PHY driver be written that would fit into the current
infrastructure.
To this end, I still think the current patch takes the best approach.
Thanks,
David Daney
next prev parent reply other threads:[~2016-03-11 21:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 16:46 [PATCH 0/3] net/phy: Improvements to Cavium Thunder MDIO code David Daney
2016-03-11 16:47 ` [PATCH 1/3] net: thunderx: Cleanup PHY probing code David Daney
2016-03-11 17:31 ` Andrew Lunn
2016-03-11 17:41 ` David Daney
2016-03-11 18:00 ` Andrew Lunn
2016-03-11 18:26 ` David Daney
2016-03-11 19:06 ` Andrew Lunn
2016-03-11 19:34 ` David Daney
2016-03-11 19:37 ` Florian Fainelli
2016-03-11 20:56 ` David Daney
2016-03-11 21:35 ` Andrew Lunn
2016-03-11 21:57 ` David Daney [this message]
2016-03-11 16:47 ` [PATCH 2/3] phy: mdio-octeon: Refactor into two files/modules David Daney
2016-03-11 16:47 ` [PATCH 3/3] phy: mdio-thunder: Add driver for Cavium Thunder SoC MDIO buses David Daney
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=56E33F64.2000208@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=rchintakuntla@cavium.com \
--cc=robh+dt@kernel.org \
--cc=rric@kernel.org \
--cc=sgoutham@cavium.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).