From: "Neftin, Sasha" <sasha.neftin@intel.com>
To: <kovalev@altlinux.org>, <jesse.brandeburg@intel.com>,
<anthony.l.nguyen@intel.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <jeffrey.t.kirsher@intel.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
"Neftin, Sasha" <sasha.neftin@intel.com>,
"Fuxbrumer, Devora" <devora.fuxbrumer@intel.com>,
naamax.meir <naamax.meir@linux.intel.com>,
"Avivi, Amir" <amir.avivi@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH] e1000e: Add "cnp" PCH boards to the packet loss fixing workaround
Date: Sun, 14 May 2023 14:30:48 +0300 [thread overview]
Message-ID: <d0f5a242-6f11-4a8d-57e7-92bba7a9365a@intel.com> (raw)
In-Reply-To: <20230514093428.113471-1-kovalev@altlinux.org>
On 5/14/2023 12:34, kovalev@altlinux.org wrote:
> From: Vasiliy Kovalev <kovalev@altlinux.org>
>
> Add CannonLake and some Comet Lake Client Platform into the range
> of workaround for packet loss issue.
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=217436
> Fixes: 639e298f432fb0 ("e1000e: Fix packet loss on Tiger Lake and later")
> Signed-off-by: Vasiliy Kovalev <kovalev@altlinux.org>
> ---
> drivers/net/ethernet/intel/e1000e/ich8lan.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/e1000e/ich8lan.c b/drivers/net/ethernet/intel/e1000e/ich8lan.c
> index 9466f65a6da77..e233a0b93bcf1 100644
> --- a/drivers/net/ethernet/intel/e1000e/ich8lan.c
> +++ b/drivers/net/ethernet/intel/e1000e/ich8lan.c
> @@ -4875,7 +4875,7 @@ static s32 e1000_init_hw_ich8lan(struct e1000_hw *hw)
> /* Enable workaround for packet loss issue on TGP PCH
%s/TGP/CMP - In case we go in this direction.
> * Do not gate DMA clock from the modPHY block
> */
> - if (mac->type >= e1000_pch_tgp) {
> + if (mac->type >= e1000_pch_cnp) {
> fflt_dbg = er32(FFLT_DBG);
> fflt_dbg |= E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK;
> ew32(FFLT_DBG, fflt_dbg);
It is a bit better. Let's clarify a few points before continuing.
1. I realized all components on your board are ADL-P. (lspci_npk.txt). I
now aware (I will ask around) about combination of ADL and old 1Gbe
controller.
Where did you get this board? My concern is that the wrong BIOS/IFWI is
in use for this platform. 1Gbe controller may come up with corrupted
initial HW values. (NVM of controller is corrupted, in this case, we
will face a much worst platform behavior)
2. Need confirmation that writing to the 'FFLT_DBG' register is harmless
for the CML platform.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-05-14 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 9:34 [Intel-wired-lan] [PATCH] e1000e: Add "cnp" PCH boards to the packet loss fixing workaround kovalev
2023-05-14 11:30 ` Neftin, Sasha [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d0f5a242-6f11-4a8d-57e7-92bba7a9365a@intel.com \
--to=sasha.neftin@intel.com \
--cc=amir.avivi@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=devora.fuxbrumer@intel.com \
--cc=dima.ruinskiy@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kovalev@altlinux.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naamax.meir@linux.intel.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox