[Intel-wired-lan] [iwl-net][PATCH v3] e1000e: move force SMBUS near the end of enable_ulp function
Krzysztof Kozlowski
krzk at kernel.org
Tue Jun 4 13:51:18 UTC 2024
On 17/05/2024 15:50, Hui Wang wrote:
> The commit 861e8086029e ("e1000e: move force SMBUS from enable ulp
> function to avoid PHY loss issue") introduces a regression on
> PCH_MTP_I219_LM18 (PCIID: 0x8086550A). Without the referred commit, the
> ethernet works well after suspend and resume, but after applying the
> commit, the ethernet couldn't work anymore after the resume and the
> dmesg shows that the NIC link changes to 10Mbps (1000Mbps originally):
>
> [ 43.305084] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Full Duplex, Flow Control: Rx/Tx
>
> Without the commit, the force SMBUS code will not be executed if
> "return 0" or "goto out" is executed in the enable_ulp(), and in my
> case, the "goto out" is executed since FWSM_FW_VALID is set. But after
> applying the commit, the force SMBUS code will be ran unconditionally.
>
> Here move the force SMBUS code back to enable_ulp() and put it
> immediately ahead of hw->phy.ops.release(hw), this could allow the
> longest settling time as possible for interface in this function and
> doesn't change the original code logic.
>
> The issue was found on a Lenovo laptop with the ethernet hw as below:
> 00:1f.6 Ethernet controller [0200]: Intel Corporation Device [8086:550a]
> (rev 20).
>
> And this patch is verified (cable plug and unplug, system suspend
> and resume) on Lenovo laptops with ethernet hw: [8086:550a],
> [8086:550b], [8086:15bb], [8086:15be], [8086:1a1f], [8086:1a1c] and
> [8086:0dc7].
>
> Fixes: 861e8086029e ("e1000e: move force SMBUS from enable ulp function to avoid PHY loss issue")
> Signed-off-by: Hui Wang <hui.wang at canonical.com>
> Acked-by: Vitaly Lifshits <vitaly.lifshits at intel.com>
> Tested-by: Naama Meir <naamax.meir at linux.intel.com>
> Reviewed-by: Simon Horman <horms at kernel.org>
> Reviewed-by: Paul Menzel <pmenzel at molgen.mpg.de>
Where did you receive Paul's tag? Please point to the lore link
documenting it.
In other patchsets tags were made up without real review, thus I have
doubts also here.
Best regards,
Krzysztof
More information about the Intel-wired-lan
mailing list