summaryrefslogtreecommitdiff
path: root/scripts/stackusage
diff options
context:
space:
mode:
authorAlexander Duyck <alexanderduyck@fb.com>2025-11-21 19:40:16 +0300
committerPaolo Abeni <pabeni@redhat.com>2025-11-27 12:41:31 +0300
commit3f29dd34f75a09ee7f8333305618edb44617d835 (patch)
tree3e0933b551a4f1d887fb83acb74973bb1e9dd90c /scripts/stackusage
parent39e138173ae7641e952b456d2de7ad2ac03e8d88 (diff)
downloadlinux-3f29dd34f75a09ee7f8333305618edb44617d835.tar.xz
net: pcs: xpcs: Add support for FBNIC 25G, 50G, 100G PMD
The fbnic driver is planning to make use of the XPCS driver to enable support for PCS and better integration with phylink. To do this though we will need to enable several workarounds since the PMD interface for fbnic is likely to be unique since it is a mix of two different vendor products with a unique wrapper around the IP. I have generated a PHY identifier based on IEEE 802.3-2022 22.2.4.3.1 using an OUI belonging to Meta Platforms and used with our NICs. Using this we will provide it as the PMD ID via the SW based MDIO interface so that the fbnic device can be identified and necessary workarounds enabled in the XPCS driver. As an initial workaround this change adds an exception so that soft_reset is not set when the driver is initially bound to the PCS. In addition I have added logic to integrate the PMD Rx signal detect state into the link state for the PCS. With this we can avoid the link coming up too soon on the FBNIC PMD and as a result of it being in the training state so we can avoid link flaps. Signed-off-by: Alexander Duyck <alexanderduyck@fb.com> Link: https://patch.msgid.link/176374321695.959489.6648161125012056619.stgit@ahduyck-xeon-server.home.arpa Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions