> -----Original Message----- > From: Intel-wired-lan <[email protected]> On Behalf Of > Jedrzej Jagielski > Sent: Thursday, August 28, 2025 11:52 AM > To: [email protected] > Cc: Nguyen, Anthony L <[email protected]>; > [email protected]; [email protected]; Jagielski, Jedrzej > <[email protected]>; Kitszel, Przemyslaw > <[email protected]>; Loktionov, Aleksandr > <[email protected]> > Subject: [Intel-wired-lan] [PATCH iwl-net v1 1/4] ixgbevf: fix getting link > speed > data for E610 devices > > E610 adapters no longer use the VFLINKS register to read PF's link speed and > linkup state. As a result VF driver cannot get actual link state and it > incorrectly > reports 10G which is the default option. > It leads to a situation where even 1G adapters print 10G as actual link speed. > The same happens when PF driver set speed different than 10G. > > Add new mailbox operation to let the VF driver request a PF driver to provide > actual link data. Update the mailbox api to v1.6. > > Incorporate both ways of getting link status within the legacy > ixgbe_check_mac_link_vf() function. > > Fixes: 4c44b450c69b ("ixgbevf: Add support for Intel(R) E610 device") > Co-developed-by: Andrzej Wilczynski <[email protected]> > Signed-off-by: Andrzej Wilczynski <[email protected]> > Reviewed-by: Przemek Kitszel <[email protected]> > Reviewed-by: Aleksandr Loktionov <[email protected]> > Cc: [email protected] > Signed-off-by: Jedrzej Jagielski <[email protected]> > --- > drivers/net/ethernet/intel/ixgbevf/defines.h | 1 + > .../net/ethernet/intel/ixgbevf/ixgbevf_main.c | 6 +- > drivers/net/ethernet/intel/ixgbevf/mbx.h | 4 + > drivers/net/ethernet/intel/ixgbevf/vf.c | 137 ++++++++++++++---- > 4 files changed, 116 insertions(+), 32 deletions(-) > > diff --git a/drivers/net/ethernet/intel/ixgbevf/defines.h > b/drivers/net/ethernet/intel/ixgbevf/defines.h > index a9bc96f6399d..e177d1d58696 100644 > --- a/drivers/net/ethernet/intel/ixgbevf/defines.h > +++ b/drivers/net/ethernet/intel/ixgbevf/defines.h > @@ -28,6 +28,7 @@
Tested-by: Rafal Romanowski <[email protected]>
