> i've checked the scenario and, indeed, EEE gets reenabled once link
> conditions are meet again even without driver intervention.
> Thanks for pointing me that.
> In that case i will remove link enablement/disablement on driver side,
> but i am wondering whether leaving logging trace on link condition
> change (EEE gets disabled due to unsupported link conditions) would be
> beneficial
> WDUT?
> then keeping tristate EEE would be required i believe
The current phylib/phylink code does not log this. There is also not
much the user can do about it, if EEE is disabled, other than throw
the ixgbe out and get a card which does implement EEE at lower speeds.
Andrew
