phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
#ifndef NETDEV_PCS_H
|
|
|
|
|
#define NETDEV_PCS_H
|
|
|
|
|
|
|
|
|
|
#include <linux/phy.h>
|
|
|
|
|
#include <linux/spinlock.h>
|
|
|
|
|
#include <linux/workqueue.h>
|
|
|
|
|
|
|
|
|
|
struct device_node;
|
|
|
|
|
struct ethtool_cmd;
|
2017-12-01 03:25:09 -07:00
|
|
|
struct fwnode_handle;
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
struct net_device;
|
|
|
|
|
|
|
|
|
|
enum {
|
|
|
|
|
MLO_PAUSE_NONE,
|
2020-02-15 08:49:53 -07:00
|
|
|
MLO_PAUSE_RX = BIT(0),
|
|
|
|
|
MLO_PAUSE_TX = BIT(1),
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
MLO_PAUSE_TXRX_MASK = MLO_PAUSE_TX | MLO_PAUSE_RX,
|
2020-02-15 08:49:53 -07:00
|
|
|
MLO_PAUSE_AN = BIT(2),
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
|
|
|
|
|
MLO_AN_PHY = 0, /* Conventional PHY */
|
|
|
|
|
MLO_AN_FIXED, /* Fixed-link mode */
|
2017-12-01 03:24:26 -07:00
|
|
|
MLO_AN_INBAND, /* In-band protocol */
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static inline bool phylink_autoneg_inband(unsigned int mode)
|
|
|
|
|
{
|
2017-12-01 03:24:26 -07:00
|
|
|
return mode == MLO_AN_INBAND;
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
}
|
|
|
|
|
|
2017-12-01 03:24:47 -07:00
|
|
|
/**
|
|
|
|
|
* struct phylink_link_state - link state structure
|
|
|
|
|
* @advertising: ethtool bitmask containing advertised link modes
|
|
|
|
|
* @lp_advertising: ethtool bitmask containing link partner advertised link
|
|
|
|
|
* modes
|
|
|
|
|
* @interface: link &typedef phy_interface_t mode
|
|
|
|
|
* @speed: link speed, one of the SPEED_* constants.
|
|
|
|
|
* @duplex: link duplex mode, one of DUPLEX_* constants.
|
|
|
|
|
* @pause: link pause state, described by MLO_PAUSE_* constants.
|
|
|
|
|
* @link: true if the link is up.
|
|
|
|
|
* @an_enabled: true if autonegotiation is enabled/desired.
|
|
|
|
|
* @an_complete: true if autonegotiation has completed.
|
|
|
|
|
*/
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
struct phylink_link_state {
|
|
|
|
|
__ETHTOOL_DECLARE_LINK_MODE_MASK(advertising);
|
|
|
|
|
__ETHTOOL_DECLARE_LINK_MODE_MASK(lp_advertising);
|
2017-12-01 03:24:47 -07:00
|
|
|
phy_interface_t interface;
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
int speed;
|
|
|
|
|
int duplex;
|
|
|
|
|
int pause;
|
|
|
|
|
unsigned int link:1;
|
|
|
|
|
unsigned int an_enabled:1;
|
|
|
|
|
unsigned int an_complete:1;
|
|
|
|
|
};
|
|
|
|
|
|
2019-05-28 11:38:12 -06:00
|
|
|
enum phylink_op_type {
|
|
|
|
|
PHYLINK_NETDEV = 0,
|
2019-05-28 11:38:13 -06:00
|
|
|
PHYLINK_DEV,
|
2019-05-28 11:38:12 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* struct phylink_config - PHYLINK configuration structure
|
|
|
|
|
* @dev: a pointer to a struct device associated with the MAC
|
|
|
|
|
* @type: operation type of PHYLINK instance
|
2020-01-05 18:34:11 -07:00
|
|
|
* @pcs_poll: MAC PCS cannot provide link change interrupt
|
2020-06-23 01:09:01 -06:00
|
|
|
* @poll_fixed_state: if true, starts link_poll,
|
|
|
|
|
* if MAC link is at %MLO_AN_FIXED mode.
|
|
|
|
|
* @get_fixed_state: callback to execute to determine the fixed link state,
|
|
|
|
|
* if MAC link is at %MLO_AN_FIXED mode.
|
2019-05-28 11:38:12 -06:00
|
|
|
*/
|
|
|
|
|
struct phylink_config {
|
|
|
|
|
struct device *dev;
|
|
|
|
|
enum phylink_op_type type;
|
2020-01-05 18:34:11 -07:00
|
|
|
bool pcs_poll;
|
2020-04-23 10:02:56 -06:00
|
|
|
bool poll_fixed_state;
|
|
|
|
|
void (*get_fixed_state)(struct phylink_config *config,
|
|
|
|
|
struct phylink_link_state *state);
|
2019-05-28 11:38:12 -06:00
|
|
|
};
|
|
|
|
|
|
2017-12-01 03:24:47 -07:00
|
|
|
/**
|
|
|
|
|
* struct phylink_mac_ops - MAC operations structure.
|
|
|
|
|
* @validate: Validate and update the link configuration.
|
2019-11-20 17:36:22 -07:00
|
|
|
* @mac_pcs_get_state: Read the current link state from the hardware.
|
2020-07-21 05:04:41 -06:00
|
|
|
* @mac_prepare: prepare for a major reconfiguration of the interface.
|
2017-12-01 03:24:47 -07:00
|
|
|
* @mac_config: configure the MAC for the selected mode and state.
|
2020-07-21 05:04:41 -06:00
|
|
|
* @mac_finish: finish a major reconfiguration of the interface.
|
2017-12-01 03:24:47 -07:00
|
|
|
* @mac_an_restart: restart 802.3z BaseX autonegotiation.
|
|
|
|
|
* @mac_link_down: take the link down.
|
|
|
|
|
* @mac_link_up: allow the link to come up.
|
|
|
|
|
*
|
|
|
|
|
* The individual methods are described more fully below.
|
|
|
|
|
*/
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
struct phylink_mac_ops {
|
2019-05-28 11:38:12 -06:00
|
|
|
void (*validate)(struct phylink_config *config,
|
|
|
|
|
unsigned long *supported,
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
struct phylink_link_state *state);
|
2019-11-20 17:36:22 -07:00
|
|
|
void (*mac_pcs_get_state)(struct phylink_config *config,
|
|
|
|
|
struct phylink_link_state *state);
|
2020-07-21 05:04:41 -06:00
|
|
|
int (*mac_prepare)(struct phylink_config *config, unsigned int mode,
|
|
|
|
|
phy_interface_t iface);
|
2019-05-28 11:38:12 -06:00
|
|
|
void (*mac_config)(struct phylink_config *config, unsigned int mode,
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
const struct phylink_link_state *state);
|
2020-07-21 05:04:41 -06:00
|
|
|
int (*mac_finish)(struct phylink_config *config, unsigned int mode,
|
|
|
|
|
phy_interface_t iface);
|
2019-05-28 11:38:12 -06:00
|
|
|
void (*mac_an_restart)(struct phylink_config *config);
|
|
|
|
|
void (*mac_link_down)(struct phylink_config *config, unsigned int mode,
|
2018-03-28 16:44:15 -06:00
|
|
|
phy_interface_t interface);
|
2020-02-26 03:23:41 -07:00
|
|
|
void (*mac_link_up)(struct phylink_config *config,
|
|
|
|
|
struct phy_device *phy, unsigned int mode,
|
|
|
|
|
phy_interface_t interface, int speed, int duplex,
|
|
|
|
|
bool tx_pause, bool rx_pause);
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
};
|
|
|
|
|
|
2017-12-01 03:24:47 -07:00
|
|
|
#if 0 /* For kernel-doc purposes only. */
|
|
|
|
|
/**
|
|
|
|
|
* validate - Validate and update the link configuration
|
2019-05-28 11:38:12 -06:00
|
|
|
* @config: a pointer to a &struct phylink_config.
|
2017-12-01 03:24:47 -07:00
|
|
|
* @supported: ethtool bitmask for supported link modes.
|
|
|
|
|
* @state: a pointer to a &struct phylink_link_state.
|
|
|
|
|
*
|
|
|
|
|
* Clear bits in the @supported and @state->advertising masks that
|
|
|
|
|
* are not supportable by the MAC.
|
|
|
|
|
*
|
|
|
|
|
* Note that the PHY may be able to transform from one connection
|
|
|
|
|
* technology to another, so, eg, don't clear 1000BaseX just
|
|
|
|
|
* because the MAC is unable to BaseX mode. This is more about
|
2019-06-25 03:44:33 -06:00
|
|
|
* clearing unsupported speeds and duplex settings. The port modes
|
|
|
|
|
* should not be cleared; phylink_set_port_modes() will help with this.
|
2017-12-01 03:24:47 -07:00
|
|
|
*
|
|
|
|
|
* If the @state->interface mode is %PHY_INTERFACE_MODE_1000BASEX
|
|
|
|
|
* or %PHY_INTERFACE_MODE_2500BASEX, select the appropriate mode
|
|
|
|
|
* based on @state->advertising and/or @state->speed and update
|
2019-06-25 03:44:33 -06:00
|
|
|
* @state->interface accordingly. See phylink_helper_basex_speed().
|
|
|
|
|
*
|
|
|
|
|
* When @state->interface is %PHY_INTERFACE_MODE_NA, phylink expects the
|
|
|
|
|
* MAC driver to return all supported link modes.
|
|
|
|
|
*
|
|
|
|
|
* If the @state->interface mode is not supported, then the @supported
|
|
|
|
|
* mask must be cleared.
|
2017-12-01 03:24:47 -07:00
|
|
|
*/
|
2019-05-28 11:38:12 -06:00
|
|
|
void validate(struct phylink_config *config, unsigned long *supported,
|
2017-12-01 03:24:47 -07:00
|
|
|
struct phylink_link_state *state);
|
|
|
|
|
|
|
|
|
|
/**
|
2019-11-20 17:36:22 -07:00
|
|
|
* mac_pcs_get_state() - Read the current inband link state from the hardware
|
2019-05-28 11:38:12 -06:00
|
|
|
* @config: a pointer to a &struct phylink_config.
|
2017-12-01 03:24:47 -07:00
|
|
|
* @state: a pointer to a &struct phylink_link_state.
|
|
|
|
|
*
|
2019-11-20 17:36:22 -07:00
|
|
|
* Read the current inband link state from the MAC PCS, reporting the
|
|
|
|
|
* current speed in @state->speed, duplex mode in @state->duplex, pause
|
|
|
|
|
* mode in @state->pause using the %MLO_PAUSE_RX and %MLO_PAUSE_TX bits,
|
|
|
|
|
* negotiation completion state in @state->an_complete, and link up state
|
|
|
|
|
* in @state->link. If possible, @state->lp_advertising should also be
|
|
|
|
|
* populated.
|
2017-12-01 03:24:47 -07:00
|
|
|
*/
|
2019-11-20 17:36:22 -07:00
|
|
|
void mac_pcs_get_state(struct phylink_config *config,
|
|
|
|
|
struct phylink_link_state *state);
|
2017-12-01 03:24:47 -07:00
|
|
|
|
2020-07-21 05:04:41 -06:00
|
|
|
/**
|
|
|
|
|
* mac_prepare() - prepare to change the PHY interface mode
|
|
|
|
|
* @config: a pointer to a &struct phylink_config.
|
|
|
|
|
* @mode: one of %MLO_AN_FIXED, %MLO_AN_PHY, %MLO_AN_INBAND.
|
|
|
|
|
* @iface: interface mode to switch to
|
|
|
|
|
*
|
|
|
|
|
* phylink will call this method at the beginning of a full initialisation
|
|
|
|
|
* of the link, which includes changing the interface mode or at initial
|
|
|
|
|
* startup time. It may be called for the current mode. The MAC driver
|
|
|
|
|
* should perform whatever actions are required, e.g. disabling the
|
|
|
|
|
* Serdes PHY.
|
|
|
|
|
*
|
|
|
|
|
* This will be the first call in the sequence:
|
|
|
|
|
* - mac_prepare()
|
|
|
|
|
* - mac_config()
|
|
|
|
|
* - pcs_config()
|
|
|
|
|
* - possible pcs_an_restart()
|
|
|
|
|
* - mac_finish()
|
|
|
|
|
*
|
|
|
|
|
* Returns zero on success, or negative errno on failure which will be
|
|
|
|
|
* reported to the kernel log.
|
|
|
|
|
*/
|
|
|
|
|
int mac_prepare(struct phylink_config *config, unsigned int mode,
|
|
|
|
|
phy_interface_t iface);
|
|
|
|
|
|
2017-12-01 03:24:47 -07:00
|
|
|
/**
|
|
|
|
|
* mac_config() - configure the MAC for the selected mode and state
|
2019-05-28 11:38:12 -06:00
|
|
|
* @config: a pointer to a &struct phylink_config.
|
2017-12-01 03:24:47 -07:00
|
|
|
* @mode: one of %MLO_AN_FIXED, %MLO_AN_PHY, %MLO_AN_INBAND.
|
|
|
|
|
* @state: a pointer to a &struct phylink_link_state.
|
|
|
|
|
*
|
2019-06-14 04:37:49 -06:00
|
|
|
* Note - not all members of @state are valid. In particular,
|
|
|
|
|
* @state->lp_advertising, @state->link, @state->an_complete are never
|
|
|
|
|
* guaranteed to be correct, and so any mac_config() implementation must
|
|
|
|
|
* never reference these fields.
|
|
|
|
|
*
|
2020-02-26 03:23:41 -07:00
|
|
|
* (this requires a rewrite - please refer to mac_link_up() for situations
|
|
|
|
|
* where the PCS and MAC are not tightly integrated.)
|
|
|
|
|
*
|
2020-02-15 08:50:09 -07:00
|
|
|
* In all negotiation modes, as defined by @mode, @state->pause indicates the
|
|
|
|
|
* pause settings which should be applied as follows. If %MLO_PAUSE_AN is not
|
|
|
|
|
* set, %MLO_PAUSE_TX and %MLO_PAUSE_RX indicate whether the MAC should send
|
|
|
|
|
* pause frames and/or act on received pause frames respectively. Otherwise,
|
|
|
|
|
* the results of in-band negotiation/status from the MAC PCS should be used
|
|
|
|
|
* to control the MAC pause mode settings.
|
|
|
|
|
*
|
2017-12-01 03:24:47 -07:00
|
|
|
* The action performed depends on the currently selected mode:
|
|
|
|
|
*
|
|
|
|
|
* %MLO_AN_FIXED, %MLO_AN_PHY:
|
2020-02-26 03:23:41 -07:00
|
|
|
* Configure for non-inband negotiation mode, where the link settings
|
|
|
|
|
* are completely communicated via mac_link_up(). The physical link
|
|
|
|
|
* protocol from the MAC is specified by @state->interface.
|
|
|
|
|
*
|
|
|
|
|
* @state->advertising may be used, but is not required.
|
|
|
|
|
*
|
|
|
|
|
* Older drivers (prior to the mac_link_up() change) may use @state->speed,
|
|
|
|
|
* @state->duplex and @state->pause to configure the MAC, but this is
|
|
|
|
|
* deprecated; such drivers should be converted to use mac_link_up().
|
2019-06-14 04:37:49 -06:00
|
|
|
*
|
2020-02-26 03:23:41 -07:00
|
|
|
* Other members of @state must be ignored.
|
|
|
|
|
*
|
|
|
|
|
* Valid state members: interface, advertising.
|
|
|
|
|
* Deprecated state members: speed, duplex, pause.
|
2017-12-01 03:24:47 -07:00
|
|
|
*
|
|
|
|
|
* %MLO_AN_INBAND:
|
|
|
|
|
* place the link in an inband negotiation mode (such as 802.3z
|
|
|
|
|
* 1000base-X or Cisco SGMII mode depending on the @state->interface
|
|
|
|
|
* mode). In both cases, link state management (whether the link
|
|
|
|
|
* is up or not) is performed by the MAC, and reported via the
|
2019-11-20 17:36:22 -07:00
|
|
|
* mac_pcs_get_state() callback. Changes in link state must be made
|
2017-12-01 03:24:47 -07:00
|
|
|
* by calling phylink_mac_change().
|
|
|
|
|
*
|
2020-02-15 08:50:09 -07:00
|
|
|
* Interface mode specific details are mentioned below.
|
|
|
|
|
*
|
2017-12-01 03:24:47 -07:00
|
|
|
* If in 802.3z mode, the link speed is fixed, dependent on the
|
2020-02-15 08:50:09 -07:00
|
|
|
* @state->interface. Duplex and pause modes are negotiated via
|
|
|
|
|
* the in-band configuration word. Advertised pause modes are set
|
|
|
|
|
* according to the @state->an_enabled and @state->advertising
|
|
|
|
|
* flags. Beware of MACs which only support full duplex at gigabit
|
|
|
|
|
* and higher speeds.
|
2017-12-01 03:24:47 -07:00
|
|
|
*
|
|
|
|
|
* If in Cisco SGMII mode, the link speed and duplex mode are passed
|
|
|
|
|
* in the serial bitstream 16-bit configuration word, and the MAC
|
|
|
|
|
* should be configured to read these bits and acknowledge the
|
|
|
|
|
* configuration word. Nothing is advertised by the MAC. The MAC is
|
|
|
|
|
* responsible for reading the configuration word and configuring
|
|
|
|
|
* itself accordingly.
|
2019-02-22 04:31:41 -07:00
|
|
|
*
|
2019-06-14 04:37:49 -06:00
|
|
|
* Valid state members: interface, an_enabled, pause, advertising.
|
|
|
|
|
*
|
2019-02-22 04:31:41 -07:00
|
|
|
* Implementations are expected to update the MAC to reflect the
|
|
|
|
|
* requested settings - i.o.w., if nothing has changed between two
|
|
|
|
|
* calls, no action is expected. If only flow control settings have
|
|
|
|
|
* changed, flow control should be updated *without* taking the link
|
|
|
|
|
* down. This "update" behaviour is critical to avoid bouncing the
|
|
|
|
|
* link up status.
|
2017-12-01 03:24:47 -07:00
|
|
|
*/
|
2019-05-28 11:38:12 -06:00
|
|
|
void mac_config(struct phylink_config *config, unsigned int mode,
|
2017-12-01 03:24:47 -07:00
|
|
|
const struct phylink_link_state *state);
|
|
|
|
|
|
2020-07-21 05:04:41 -06:00
|
|
|
/**
|
|
|
|
|
* mac_finish() - finish a to change the PHY interface mode
|
|
|
|
|
* @config: a pointer to a &struct phylink_config.
|
|
|
|
|
* @mode: one of %MLO_AN_FIXED, %MLO_AN_PHY, %MLO_AN_INBAND.
|
|
|
|
|
* @iface: interface mode to switch to
|
|
|
|
|
*
|
|
|
|
|
* phylink will call this if it called mac_prepare() to allow the MAC to
|
|
|
|
|
* complete any necessary steps after the MAC and PCS have been configured
|
|
|
|
|
* for the @mode and @iface. E.g. a MAC driver may wish to re-enable the
|
|
|
|
|
* Serdes PHY here if it was previously disabled by mac_prepare().
|
|
|
|
|
*
|
|
|
|
|
* Returns zero on success, or negative errno on failure which will be
|
|
|
|
|
* reported to the kernel log.
|
|
|
|
|
*/
|
|
|
|
|
int mac_finish(struct phylink_config *config, unsigned int mode,
|
|
|
|
|
phy_interface_t iface);
|
|
|
|
|
|
2017-12-01 03:24:47 -07:00
|
|
|
/**
|
|
|
|
|
* mac_an_restart() - restart 802.3z BaseX autonegotiation
|
2019-05-28 11:38:12 -06:00
|
|
|
* @config: a pointer to a &struct phylink_config.
|
2017-12-01 03:24:47 -07:00
|
|
|
*/
|
2019-05-28 11:38:12 -06:00
|
|
|
void mac_an_restart(struct phylink_config *config);
|
2017-12-01 03:24:47 -07:00
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* mac_link_down() - take the link down
|
2019-05-28 11:38:12 -06:00
|
|
|
* @config: a pointer to a &struct phylink_config.
|
2017-12-01 03:24:47 -07:00
|
|
|
* @mode: link autonegotiation mode
|
2018-03-28 16:44:15 -06:00
|
|
|
* @interface: link &typedef phy_interface_t mode
|
2017-12-01 03:24:47 -07:00
|
|
|
*
|
|
|
|
|
* If @mode is not an in-band negotiation mode (as defined by
|
|
|
|
|
* phylink_autoneg_inband()), force the link down and disable any
|
2018-03-28 16:44:15 -06:00
|
|
|
* Energy Efficient Ethernet MAC configuration. Interface type
|
|
|
|
|
* selection must be done in mac_config().
|
2017-12-01 03:24:47 -07:00
|
|
|
*/
|
2019-05-28 11:38:12 -06:00
|
|
|
void mac_link_down(struct phylink_config *config, unsigned int mode,
|
2018-03-28 16:44:15 -06:00
|
|
|
phy_interface_t interface);
|
2017-12-01 03:24:47 -07:00
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* mac_link_up() - allow the link to come up
|
2019-05-28 11:38:12 -06:00
|
|
|
* @config: a pointer to a &struct phylink_config.
|
2020-02-26 03:23:41 -07:00
|
|
|
* @phy: any attached phy
|
2017-12-01 03:24:47 -07:00
|
|
|
* @mode: link autonegotiation mode
|
2018-03-28 16:44:15 -06:00
|
|
|
* @interface: link &typedef phy_interface_t mode
|
2020-02-26 03:23:41 -07:00
|
|
|
* @speed: link speed
|
|
|
|
|
* @duplex: link duplex
|
|
|
|
|
* @tx_pause: link transmit pause enablement status
|
|
|
|
|
* @rx_pause: link receive pause enablement status
|
2017-12-01 03:24:47 -07:00
|
|
|
*
|
2020-02-26 03:23:41 -07:00
|
|
|
* Configure the MAC for an established link.
|
|
|
|
|
*
|
|
|
|
|
* @speed, @duplex, @tx_pause and @rx_pause indicate the finalised link
|
|
|
|
|
* settings, and should be used to configure the MAC block appropriately
|
|
|
|
|
* where these settings are not automatically conveyed from the PCS block,
|
|
|
|
|
* or if in-band negotiation (as defined by phylink_autoneg_inband(@mode))
|
|
|
|
|
* is disabled.
|
|
|
|
|
*
|
|
|
|
|
* Note that when 802.3z in-band negotiation is in use, it is possible
|
|
|
|
|
* that the user wishes to override the pause settings, and this should
|
|
|
|
|
* be allowed when considering the implementation of this method.
|
|
|
|
|
*
|
|
|
|
|
* If in-band negotiation mode is disabled, allow the link to come up. If
|
|
|
|
|
* @phy is non-%NULL, configure Energy Efficient Ethernet by calling
|
2017-12-01 03:24:47 -07:00
|
|
|
* phy_init_eee() and perform appropriate MAC configuration for EEE.
|
2018-03-28 16:44:15 -06:00
|
|
|
* Interface type selection must be done in mac_config().
|
2017-12-01 03:24:47 -07:00
|
|
|
*/
|
2020-02-26 03:23:41 -07:00
|
|
|
void mac_link_up(struct phylink_config *config, struct phy_device *phy,
|
|
|
|
|
unsigned int mode, phy_interface_t interface,
|
|
|
|
|
int speed, int duplex, bool tx_pause, bool rx_pause);
|
2017-12-01 03:24:47 -07:00
|
|
|
#endif
|
|
|
|
|
|
2020-07-21 05:04:46 -06:00
|
|
|
struct phylink_pcs_ops;
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* struct phylink_pcs - PHYLINK PCS instance
|
|
|
|
|
* @ops: a pointer to the &struct phylink_pcs_ops structure
|
|
|
|
|
* @poll: poll the PCS for link changes
|
|
|
|
|
*
|
|
|
|
|
* This structure is designed to be embedded within the PCS private data,
|
|
|
|
|
* and will be passed between phylink and the PCS.
|
|
|
|
|
*/
|
|
|
|
|
struct phylink_pcs {
|
|
|
|
|
const struct phylink_pcs_ops *ops;
|
|
|
|
|
bool poll;
|
|
|
|
|
};
|
|
|
|
|
|
2020-03-30 11:44:55 -06:00
|
|
|
/**
|
|
|
|
|
* struct phylink_pcs_ops - MAC PCS operations structure.
|
|
|
|
|
* @pcs_get_state: read the current MAC PCS link state from the hardware.
|
|
|
|
|
* @pcs_config: configure the MAC PCS for the selected mode and state.
|
|
|
|
|
* @pcs_an_restart: restart 802.3z BaseX autonegotiation.
|
|
|
|
|
* @pcs_link_up: program the PCS for the resolved link configuration
|
|
|
|
|
* (where necessary).
|
|
|
|
|
*/
|
|
|
|
|
struct phylink_pcs_ops {
|
2020-07-21 05:04:46 -06:00
|
|
|
void (*pcs_get_state)(struct phylink_pcs *pcs,
|
2020-03-30 11:44:55 -06:00
|
|
|
struct phylink_link_state *state);
|
2020-07-21 05:04:46 -06:00
|
|
|
int (*pcs_config)(struct phylink_pcs *pcs, unsigned int mode,
|
2020-03-30 11:44:55 -06:00
|
|
|
phy_interface_t interface,
|
2020-07-21 05:04:36 -06:00
|
|
|
const unsigned long *advertising,
|
|
|
|
|
bool permit_pause_to_mac);
|
2020-07-21 05:04:46 -06:00
|
|
|
void (*pcs_an_restart)(struct phylink_pcs *pcs);
|
|
|
|
|
void (*pcs_link_up)(struct phylink_pcs *pcs, unsigned int mode,
|
2020-03-30 11:44:55 -06:00
|
|
|
phy_interface_t interface, int speed, int duplex);
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#if 0 /* For kernel-doc purposes only. */
|
|
|
|
|
/**
|
|
|
|
|
* pcs_get_state() - Read the current inband link state from the hardware
|
2020-07-21 05:04:46 -06:00
|
|
|
* @pcs: a pointer to a &struct phylink_pcs.
|
2020-03-30 11:44:55 -06:00
|
|
|
* @state: a pointer to a &struct phylink_link_state.
|
|
|
|
|
*
|
|
|
|
|
* Read the current inband link state from the MAC PCS, reporting the
|
|
|
|
|
* current speed in @state->speed, duplex mode in @state->duplex, pause
|
|
|
|
|
* mode in @state->pause using the %MLO_PAUSE_RX and %MLO_PAUSE_TX bits,
|
|
|
|
|
* negotiation completion state in @state->an_complete, and link up state
|
|
|
|
|
* in @state->link. If possible, @state->lp_advertising should also be
|
|
|
|
|
* populated.
|
|
|
|
|
*
|
|
|
|
|
* When present, this overrides mac_pcs_get_state() in &struct
|
|
|
|
|
* phylink_mac_ops.
|
|
|
|
|
*/
|
2020-07-21 05:04:46 -06:00
|
|
|
void pcs_get_state(struct phylink_pcs *pcs,
|
2020-03-30 11:44:55 -06:00
|
|
|
struct phylink_link_state *state);
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* pcs_config() - Configure the PCS mode and advertisement
|
2020-07-21 05:04:46 -06:00
|
|
|
* @pcs: a pointer to a &struct phylink_pcs.
|
2020-03-30 11:44:55 -06:00
|
|
|
* @mode: one of %MLO_AN_FIXED, %MLO_AN_PHY, %MLO_AN_INBAND.
|
|
|
|
|
* @interface: interface mode to be used
|
|
|
|
|
* @advertising: adertisement ethtool link mode mask
|
2020-07-21 05:04:36 -06:00
|
|
|
* @permit_pause_to_mac: permit forwarding pause resolution to MAC
|
2020-03-30 11:44:55 -06:00
|
|
|
*
|
|
|
|
|
* Configure the PCS for the operating mode, the interface mode, and set
|
2020-07-21 05:04:36 -06:00
|
|
|
* the advertisement mask. @permit_pause_to_mac indicates whether the
|
|
|
|
|
* hardware may forward the pause mode resolution to the MAC.
|
2020-03-30 11:44:55 -06:00
|
|
|
*
|
|
|
|
|
* When operating in %MLO_AN_INBAND, inband should always be enabled,
|
|
|
|
|
* otherwise inband should be disabled.
|
|
|
|
|
*
|
|
|
|
|
* For SGMII, there is no advertisement from the MAC side, the PCS should
|
|
|
|
|
* be programmed to acknowledge the inband word from the PHY.
|
|
|
|
|
*
|
|
|
|
|
* For 1000BASE-X, the advertisement should be programmed into the PCS.
|
|
|
|
|
*
|
|
|
|
|
* For most 10GBASE-R, there is no advertisement.
|
|
|
|
|
*/
|
2020-07-21 05:04:46 -06:00
|
|
|
int pcs_config(struct phylink_pcs *pcs, unsigned int mode,
|
2020-08-16 16:25:49 -06:00
|
|
|
phy_interface_t interface, const unsigned long *advertising,
|
|
|
|
|
bool permit_pause_to_mac);
|
2020-03-30 11:44:55 -06:00
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* pcs_an_restart() - restart 802.3z BaseX autonegotiation
|
2020-07-21 05:04:46 -06:00
|
|
|
* @pcs: a pointer to a &struct phylink_pcs.
|
2020-03-30 11:44:55 -06:00
|
|
|
*
|
|
|
|
|
* When PCS ops are present, this overrides mac_an_restart() in &struct
|
|
|
|
|
* phylink_mac_ops.
|
|
|
|
|
*/
|
2020-07-21 05:04:46 -06:00
|
|
|
void pcs_an_restart(struct phylink_pcs *pcs);
|
2020-03-30 11:44:55 -06:00
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* pcs_link_up() - program the PCS for the resolved link configuration
|
2020-07-21 05:04:46 -06:00
|
|
|
* @pcs: a pointer to a &struct phylink_pcs.
|
2020-03-30 11:44:55 -06:00
|
|
|
* @mode: link autonegotiation mode
|
|
|
|
|
* @interface: link &typedef phy_interface_t mode
|
|
|
|
|
* @speed: link speed
|
|
|
|
|
* @duplex: link duplex
|
|
|
|
|
*
|
|
|
|
|
* This call will be made just before mac_link_up() to inform the PCS of
|
|
|
|
|
* the resolved link parameters. For example, a PCS operating in SGMII
|
|
|
|
|
* mode without in-band AN needs to be manually configured for the link
|
|
|
|
|
* and duplex setting. Otherwise, this should be a no-op.
|
|
|
|
|
*/
|
2020-07-21 05:04:46 -06:00
|
|
|
void pcs_link_up(struct phylink_pcs *pcs, unsigned int mode,
|
|
|
|
|
phy_interface_t interface, int speed, int duplex);
|
2020-03-30 11:44:55 -06:00
|
|
|
#endif
|
|
|
|
|
|
2019-05-28 11:38:12 -06:00
|
|
|
struct phylink *phylink_create(struct phylink_config *, struct fwnode_handle *,
|
|
|
|
|
phy_interface_t iface,
|
2020-03-30 11:44:50 -06:00
|
|
|
const struct phylink_mac_ops *mac_ops);
|
2020-07-21 05:04:46 -06:00
|
|
|
void phylink_set_pcs(struct phylink *, struct phylink_pcs *pcs);
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
void phylink_destroy(struct phylink *);
|
|
|
|
|
|
|
|
|
|
int phylink_connect_phy(struct phylink *, struct phy_device *);
|
2017-12-12 17:00:25 -07:00
|
|
|
int phylink_of_phy_connect(struct phylink *, struct device_node *, u32 flags);
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
void phylink_disconnect_phy(struct phylink *);
|
|
|
|
|
|
|
|
|
|
void phylink_mac_change(struct phylink *, bool up);
|
|
|
|
|
|
|
|
|
|
void phylink_start(struct phylink *);
|
|
|
|
|
void phylink_stop(struct phylink *);
|
|
|
|
|
|
|
|
|
|
void phylink_ethtool_get_wol(struct phylink *, struct ethtool_wolinfo *);
|
|
|
|
|
int phylink_ethtool_set_wol(struct phylink *, struct ethtool_wolinfo *);
|
|
|
|
|
|
|
|
|
|
int phylink_ethtool_ksettings_get(struct phylink *,
|
|
|
|
|
struct ethtool_link_ksettings *);
|
|
|
|
|
int phylink_ethtool_ksettings_set(struct phylink *,
|
|
|
|
|
const struct ethtool_link_ksettings *);
|
|
|
|
|
int phylink_ethtool_nway_reset(struct phylink *);
|
|
|
|
|
void phylink_ethtool_get_pauseparam(struct phylink *,
|
|
|
|
|
struct ethtool_pauseparam *);
|
|
|
|
|
int phylink_ethtool_set_pauseparam(struct phylink *,
|
|
|
|
|
struct ethtool_pauseparam *);
|
|
|
|
|
int phylink_get_eee_err(struct phylink *);
|
2019-02-11 04:46:06 -07:00
|
|
|
int phylink_init_eee(struct phylink *, bool);
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
int phylink_ethtool_get_eee(struct phylink *, struct ethtool_eee *);
|
|
|
|
|
int phylink_ethtool_set_eee(struct phylink *, struct ethtool_eee *);
|
|
|
|
|
int phylink_mii_ioctl(struct phylink *, struct ifreq *, int);
|
2020-06-24 04:06:54 -06:00
|
|
|
int phylink_speed_down(struct phylink *pl, bool sync);
|
|
|
|
|
int phylink_speed_up(struct phylink *pl);
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
|
|
|
|
|
#define phylink_zero(bm) \
|
|
|
|
|
bitmap_zero(bm, __ETHTOOL_LINK_MODE_MASK_NBITS)
|
|
|
|
|
#define __phylink_do_bit(op, bm, mode) \
|
|
|
|
|
op(ETHTOOL_LINK_MODE_ ## mode ## _BIT, bm)
|
|
|
|
|
|
|
|
|
|
#define phylink_set(bm, mode) __phylink_do_bit(__set_bit, bm, mode)
|
|
|
|
|
#define phylink_clear(bm, mode) __phylink_do_bit(__clear_bit, bm, mode)
|
|
|
|
|
#define phylink_test(bm, mode) __phylink_do_bit(test_bit, bm, mode)
|
|
|
|
|
|
|
|
|
|
void phylink_set_port_modes(unsigned long *bits);
|
2018-08-09 07:38:38 -06:00
|
|
|
void phylink_helper_basex_speed(struct phylink_link_state *state);
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
|
2020-03-17 08:52:36 -06:00
|
|
|
void phylink_mii_c22_pcs_get_state(struct mdio_device *pcs,
|
|
|
|
|
struct phylink_link_state *state);
|
|
|
|
|
int phylink_mii_c22_pcs_set_advertisement(struct mdio_device *pcs,
|
2020-03-30 11:44:44 -06:00
|
|
|
phy_interface_t interface,
|
|
|
|
|
const unsigned long *advertising);
|
2020-07-21 05:04:51 -06:00
|
|
|
int phylink_mii_c22_pcs_config(struct mdio_device *pcs, unsigned int mode,
|
|
|
|
|
phy_interface_t interface,
|
|
|
|
|
const unsigned long *advertising);
|
2020-03-17 08:52:36 -06:00
|
|
|
void phylink_mii_c22_pcs_an_restart(struct mdio_device *pcs);
|
|
|
|
|
|
2020-03-17 08:52:41 -06:00
|
|
|
void phylink_mii_c45_pcs_get_state(struct mdio_device *pcs,
|
|
|
|
|
struct phylink_link_state *state);
|
2020-08-30 02:33:58 -06:00
|
|
|
|
|
|
|
|
void phylink_decode_usxgmii_word(struct phylink_link_state *state,
|
|
|
|
|
uint16_t lpa);
|
phylink: add phylink infrastructure
The link between the ethernet MAC and its PHY has become more complex
as the interface evolves. This is especially true with serdes links,
where the part of the PHY is effectively integrated into the MAC.
Serdes links can be connected to a variety of devices, including SFF
modules soldered down onto the board with the MAC, a SFP cage with
a hotpluggable SFP module which may contain a PHY or directly modulate
the serdes signals onto optical media with or without a PHY, or even
a classical PHY connection.
Moreover, the negotiation information on serdes links comes in two
varieties - SGMII mode, where the PHY provides its speed/duplex/flow
control information to the MAC, and 1000base-X mode where both ends
exchange their abilities and each resolve the link capabilities.
This means we need a more flexible means to support these arrangements,
particularly with the hotpluggable nature of SFP, where the PHY can
be attached or detached after the network device has been brought up.
Ethtool information can come from multiple sources:
- we may have a PHY operating in either SGMII or 1000base-X mode, in
which case we take ethtool/mii data directly from the PHY.
- we may have a optical SFP module without a PHY, with the MAC
operating in 1000base-X mode - the ethtool/mii data needs to come
from the MAC.
- we may have a copper SFP module with a PHY whic can't be accessed,
which means we need to take ethtool/mii data from the MAC.
Phylink aims to solve this by providing an intermediary between the
MAC and PHY, providing a safe way for PHYs to be hotplugged, and
allowing a SFP driver to reconfigure the serdes connection.
Phylink also takes over support of fixed link connections, where the
speed/duplex/flow control are fixed, but link status may be controlled
by a GPIO signal. By avoiding the fixed-phy implementation, phylink
can provide a faster response to link events: fixed-phy has to wait for
phylib to operate its state machine, which can take several seconds.
In comparison, phylink takes milliseconds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
- remove sync status
- rework supported and advertisment handling
- add 1000base-x speed for fixed links
- use functionality exported from phy-core, reworking
__phylink_ethtool_ksettings_set for it
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-07-25 08:03:13 -06:00
|
|
|
#endif
|