[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cb3e9c4b-a4eb-4ed5-b0aa-ec614076b6e6@linux.intel.com>
Date: Thu, 2 May 2024 10:00:07 +0300
From: "naamax.meir" <naamax.meir@...ux.intel.com>
To: Hui Wang <hui.wang@...onical.com>, intel-wired-lan@...ts.osuosl.org,
netdev@...r.kernel.org, jesse.brandeburg@...el.com,
anthony.l.nguyen@...el.com, vitaly.lifshits@...el.com,
dima.ruinskiy@...el.com
Subject: Re: [Intel-wired-lan] [PATCH] e1000e: move force SMBUS near the end
of enable_ulp function
On 4/13/2024 12:27, Hui Wang wrote:
> The commit 861e8086029e ("e1000e: move force SMBUS from enable ulp
> function to avoid PHY loss issue") introduces a regression on
> CH_MTP_I219_LM18 (PCIID: 0x8086550A). Without this 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
> immediate 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.
>
> Fixes: 861e8086029e ("e1000e: move force SMBUS from enable ulp function to avoid PHY loss issue")
> Signed-off-by: Hui Wang <hui.wang@...onical.com>
> ---
> drivers/net/ethernet/intel/e1000e/ich8lan.c | 19 +++++++++++++++++++
> drivers/net/ethernet/intel/e1000e/netdev.c | 18 ------------------
> 2 files changed, 19 insertions(+), 18 deletions(-)
Tested-by: Naama Meir <naamax.meir@...ux.intel.com>
Powered by blists - more mailing lists