Lines Matching +full:single +full:- +full:link

1 .. SPDX-License-Identifier: GPL-2.0
5 PHY link topology
11 The PHY link topology representation in the networking stack aims at representing
12 the hardware layout for any given Ethernet link.
17 when designing these configuration APIs were that the link looks something like ::
19   +-----------------------+        +----------+      +--------------+
21   |       MAC             | ------ |   PHY    | ---- |    Port      | ---... to LP
22   +-----------------------+        +----------+      +--------------+
35 The link topology then looks like this (when an SFP module is inserted) ::
37   +-----+  SGMII  +------------+
38   | MAC | ------- | SFP Module |
39   +-----+         +------------+
41 Knowing that some modules embed a PHY, the actual link is more like ::
43   +-----+  SGMII   +--------------+
44   | MAC | -------- | PHY (on SFP) |
45   +-----+          +--------------+
52 as media-converters, to translate the non-serialized MAC MII interface to a
55   +-----+  RGMII  +-----------------------+  SGMII  +--------------+
56   | MAC | ------- | PHY (media converter) | ------- | PHY (on SFP) |
57   +-----+         +-----------------------+         +--------------+
59 This is where the model of having a single net_device.phydev pointer shows its
60 limitations, as we now have 2 PHYs on the link.
63 PHY on the link, for use by both kernel drivers and subsystems, but also to
70 The :c:type:`struct phy_link_topology <phy_link_topology>` is a per-netdevice
90 upstream is phylink (so, no media-converter).
100 There exist a set of netlink commands to query the link topology from userspace,
101 see ``Documentation/networking/ethtool-netlink.rst``.
108 to be passed in the request to filter the DUMP to a single net_device.
115   cable testing on a given PHY on the link (most likely the outermost PHY)
116 * ``ETHTOOL_MSG_PSE_SET`` and ``ETHTOOL_MSG_PSE_GET`` for PHY-controlled PoE and PSE settings