netdev - Re: [RFC PATCH net-next 3/8] net: phy: Allow PHY devices to identify themselves as Ethernet switches

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150430125658.GB22831@lunn.ch>
Date:	Thu, 30 Apr 2015 14:56:58 +0200
From:	Andrew Lunn <andrew@...n.ch>
To:	Florian Fainelli <f.fainelli@...il.com>
Cc:	netdev@...r.kernel.org, dave@...emloft.net,
	vivien.didelot@...oirfairelinux.com,
	jerome.oufella@...oirfairelinux.com, linux@...ck-us.net,
	cphealy@...il.com, mathieu@...eaurora.org, jonasj76@...il.com,
	andrey.volkov@...vision.fr, Chris.Packham@...iedtelesis.co.nz
Subject: Re: [RFC PATCH net-next 3/8] net: phy: Allow PHY devices to identify
 themselves as Ethernet switches

On Wed, Apr 29, 2015 at 06:57:39PM -0700, Florian Fainelli wrote:
> Some Ethernet MAC drivers using the PHY library require the hardcoding
> of link parameters when interfaced to a switch device. This has
> typically lead to various ad-hoc implementations looking like this:
> 
> - using a "fixed PHY" emulated device, which will provide link
>   indication towards the Ethernet MAC driver and hardware
> 
> - pretend there is no PHY and hardcode link parameters, ala mv643x_eth
> 
> Based on that, it is desireable to have the PHY drivers advertise the
> correct link parameters, just like regular Ethernet PHYs towards their
> CPU Ethernet MAC drivers, however, Ethernet MAC drivers should be able
> to tell whether this link should be monitored or not. In the context of
> an Ethernet switch, we do not need to monitor this link since it should
> be always up.
> 
> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
> ---
>  include/linux/phy.h | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/include/linux/phy.h b/include/linux/phy.h
> index 685809835b5c..52fc64874fdb 100644
> --- a/include/linux/phy.h
> +++ b/include/linux/phy.h
> @@ -327,6 +327,7 @@ struct phy_c45_device_ids {
>   * c45_ids: 802.3-c45 Device Identifers if is_c45.
>   * is_c45:  Set to true if this phy uses clause 45 addressing.
>   * is_internal: Set to true if this phy is internal to a MAC.
> + * is_switch: Set to true if this phy is an Ethernet switch.
>   * has_fixups: Set to true if this phy has fixups/quirks.
>   * suspended: Set to true if this phy has been suspended successfully.
>   * state: state of the PHY for management purposes
> @@ -365,6 +366,7 @@ struct phy_device {
>  	struct phy_c45_device_ids c45_ids;
>  	bool is_c45;
>  	bool is_internal;
> +	bool is_switch;

Hi Florian

I have another two use cases for fixed_phy which i'm thinking about
implementing soon. Both require putting a fixed_phy into DSA port
properties in DT.

The first is when the CPU ethernet and the switch don't have the same
speed capabilities. At the moment, the switch driver configures the
CPU port to its maximum speed. But i know of a board coming soon with
gigabit switch ports, but the CPU Ethernet is only fast Ethernet.

When switch ports are connected to an SFP module, not a copper phy. A
fixed phy allows the switch to be configured to the correct
speed/duplex to match the SFP module.

So in this respect, i'm wondering if is_switch is the best of names?

   Andrew
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html