On Thu, Sep 24, 2026 at 11:34:04AM +0200, Burakov, Anatoly wrote:
> On 9/23/2026 1:25 PM, Sandeep Penigalapati wrote:
> > On 82599 and X5xx, EICR bit 0x00200000 is the MACsec PN-threshold cause
> > (IXGBE_EICR_LINKSEC). On E610 the very same bit is redefined as the
> > asynchronous firmware event cause (IXGBE_EICR_FW_EVENT). The interrupt
> > handler decoded this bit unconditionally as LINKSEC and raised
> > RTE_ETH_EVENT_MACSEC.
> >
> > As E610 does not support MACsec, every firmware event (for example a
> > link change) was reported to the application as a spurious MACsec event.
> > In addition, the firmware events posted on the Admin Command Interface
> > (ACI) receive queue were never drained, so the cause was not cleared.
> >
> > Decode the bit per MAC type: on E610 treat it as a firmware event and
> > drain the ACI receive queue until empty; keep the MACsec handling for
> > the other MAC types. Link changes continue to be handled through the
> > existing IXGBE_EICR_LSC path.
> >
> > Fixes: 316637762a5f ("net/ixgbe/base: enable E610 device")
> > Cc: [email protected]
> > Signed-off-by: Sandeep Penigalapati <[email protected]>
> > ---
>
> Reviewed-by: Anatoly Burakov <[email protected]>
>
Applied to dpdk-next-net-intel.
Thanks,
/Bruce
