[PATCH v2 2/6] common/sfc_efx/base: indicate dummy netport properties on VF
Ivan Malov
ivan.malov at arknetworks.am
Wed Aug 12 19:10:59 CEST 2026
Starting with MCFW version 1.4.0.8, Medford4 adapters support the use
of the netport MCDI for port configuration by a VF; however, the MCDI
which retrieves fixed port properties is not permitted for use by VFs.
Fill in dummy values sufficient for the DPDK driver to start on a VF.
Signed-off-by: Ivan Malov <ivan.malov at arknetworks.am>
Reviewed-by: Andy Moreton <andy.moreton at amd.com>
---
drivers/common/sfc_efx/base/efx_np.c | 26 ++++++++++++++++++++++----
1 file changed, 22 insertions(+), 4 deletions(-)
diff --git a/drivers/common/sfc_efx/base/efx_np.c b/drivers/common/sfc_efx/base/efx_np.c
index 0e1cd35591..7a30567fe0 100644
--- a/drivers/common/sfc_efx/base/efx_np.c
+++ b/drivers/common/sfc_efx/base/efx_np.c
@@ -240,6 +240,7 @@ efx_np_get_fixed_port_props(
__out_opt uint32_t *sup_cap_maskp,
__out_opt efx_qword_t *loopback_cap_maskp)
{
+ const efx_nic_cfg_t *encp = &enp->en_nic_cfg;
EFX_MCDI_DECLARE_BUF(payload,
MC_CMD_GET_FIXED_PORT_PROPERTIES_IN_LEN,
MC_CMD_GET_FIXED_PORT_PROPERTIES_OUT_V2_LEN);
@@ -247,6 +248,10 @@ efx_np_get_fixed_port_props(
efx_mcdi_req_t req;
efx_rc_t rc;
+ /* VFs do not allow access to the fixed port data. */
+ if (EFX_PCI_FUNCTION_IS_VF(encp))
+ return (0);
+
req.emr_out_length = MC_CMD_GET_FIXED_PORT_PROPERTIES_OUT_V2_LEN;
req.emr_in_length = MC_CMD_GET_FIXED_PORT_PROPERTIES_IN_LEN;
req.emr_cmd = MC_CMD_GET_FIXED_PORT_PROPERTIES;
@@ -1050,10 +1055,6 @@ efx_np_attach(
if (rc != 0)
goto fail1;
- /*
- * FIXME: This may need revisiting for VFs, which
- * don't necessarily have access to these details.
- */
rc = efx_np_get_fixed_port_props(enp, epp->ep_np_handle,
epp->ep_np_cap_data_raw, &epp->ep_phy_cap_mask,
&epp->ep_np_loopback_cap_mask);
@@ -1071,6 +1072,23 @@ efx_np_attach(
epp->ep_phy_cap_mask |= 1U << EFX_PHY_CAP_AN;
}
+ /*
+ * On VFs, 'efx_np_get_fixed_port_props' does not report any link
+ * speeds; however, 'efx_np_link_state' should provide clues as
+ * to which link speed is de facto active on the VF. Use this
+ * clue to provide accurate information to the application.
+ *
+ * Also, indicate three basic capabilities that the VF cannot
+ * manage, but that can be safely assumed to be available.
+ */
+ if (EFX_PCI_FUNCTION_IS_VF(encp)) {
+ epp->ep_phy_cap_mask = epp->ep_adv_cap_mask;
+
+ epp->ep_phy_cap_mask |= 1U << EFX_PHY_CAP_PAUSE;
+ epp->ep_phy_cap_mask |= 1U << EFX_PHY_CAP_ASYM;
+ epp->ep_phy_cap_mask |= 1U << EFX_PHY_CAP_AN;
+ }
+
#if EFSYS_OPT_LOOPBACK
efx_np_assign_loopback_props(enp);
#endif /* EFSYS_OPT_LOOPBACK */
--
2.47.3
More information about the dev
mailing list