linux-kernel - Re: [PATCH 1/3] net: thunderx: Cleanup PHY probing code.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <56E33F64.2000208@caviumnetworks.com>
Date:	Fri, 11 Mar 2016 13:57:56 -0800
From:	David Daney <ddaney@...iumnetworks.com>
To:	Andrew Lunn <andrew@...n.ch>
CC:	David Daney <ddaney.cavm@...il.com>,
	Florian Fainelli <f.fainelli@...il.com>,
	Mark Rutland <mark.rutland@....com>,
	Robert Richter <rric@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	<netdev@...r.kernel.org>, David Daney <david.daney@...ium.com>,
	<linux-kernel@...r.kernel.org>, Rob Herring <robh+dt@...nel.org>,
	Kumar Gala <galak@...eaurora.org>,
	Sunil Goutham <sgoutham@...ium.com>,
	Radha Mohan Chintakuntla <rchintakuntla@...ium.com>,
	"David S. Miller" <davem@...emloft.net>,
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/3] net: thunderx: Cleanup PHY probing code.

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