From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7E0F545804 for ; Fri, 23 Aug 2024 18:20:24 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 79DEA43382; Fri, 23 Aug 2024 18:20:24 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 7D68F4338F for ; Fri, 23 Aug 2024 18:20:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1724430023; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fpUE1Po8xn811pP99TCiI+jKoycV10osWz6lgfVv5gc=; b=BFOBsvFyOl5Acyf00zgh0obKXipno4RfZD69W7GWdjHx3IGOY1PTD77uiozpRNuAZ5mK4H wQDJdGLm0XS6vQOrou1H4d1jVXOS7uZOKuy7byBrJIqjy+sS1CraMSU/o3nEIZbt0fZXEP wlR5C1/KC6rTjHDFGRBxeZQfuH6NzRo= Received: from mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-335-A8uVbcu0NVu5PSc9DKzicw-1; Fri, 23 Aug 2024 12:20:19 -0400 X-MC-Unique: A8uVbcu0NVu5PSc9DKzicw-1 Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 0DD121955D4B; Fri, 23 Aug 2024 16:20:19 +0000 (UTC) Received: from rh.redhat.com (unknown [10.39.193.224]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id A9EA41955F45; Fri, 23 Aug 2024 16:20:17 +0000 (UTC) From: Kevin Traynor To: Venkat Kumar Ande Cc: Selwin Sebastian , dpdk stable Subject: patch 'net/axgbe: fix fluctuations for 1G Bel Fuse SFP' has been queued to stable release 21.11.8 Date: Fri, 23 Aug 2024 17:17:27 +0100 Message-ID: <20240823161929.1004778-19-ktraynor@redhat.com> In-Reply-To: <20240823161929.1004778-1-ktraynor@redhat.com> References: <20240823161929.1004778-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Hi, FYI, your patch has been queued to stable release 21.11.8 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 08/28/24. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/kevintraynor/dpdk-stable This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable/commit/8d53ecbbf62d7a7496283a7572d5f3de1bcfe36d Thanks. Kevin --- >From 8d53ecbbf62d7a7496283a7572d5f3de1bcfe36d Mon Sep 17 00:00:00 2001 From: Venkat Kumar Ande Date: Tue, 4 Jun 2024 17:41:35 +0530 Subject: [PATCH] net/axgbe: fix fluctuations for 1G Bel Fuse SFP [ upstream commit 3abfda0f7d58b2eef20cdf8e102825678b150421 ] Frequent link up/down events can happen when a Bel Fuse SFP part is connected to the amd-xgbe device. Try to avoid the frequent link issues by resetting the PHY as documented in Bel Fuse SFP datasheet. Without the fix user will see continuous port link up and down. Fixes: a5c7273771e8 ("net/axgbe: add phy programming APIs") Signed-off-by: Venkat Kumar Ande Acked-by: Selwin Sebastian --- drivers/net/axgbe/axgbe_phy_impl.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/net/axgbe/axgbe_phy_impl.c b/drivers/net/axgbe/axgbe_phy_impl.c index df334749e9..a458722e2e 100644 --- a/drivers/net/axgbe/axgbe_phy_impl.c +++ b/drivers/net/axgbe/axgbe_phy_impl.c @@ -578,4 +578,7 @@ static bool axgbe_phy_belfuse_parse_quirks(struct axgbe_port *pdata) return false; + /* Reset PHY - wait for self-clearing reset bit to clear */ + pdata->phy_if.phy_impl.reset(pdata); + if (!memcmp(&sfp_eeprom->base[AXGBE_SFP_BASE_VENDOR_PN], AXGBE_BEL_FUSE_PARTNO, strlen(AXGBE_BEL_FUSE_PARTNO))) { -- 2.46.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2024-08-23 17:18:10.574028543 +0100 +++ 0019-net-axgbe-fix-fluctuations-for-1G-Bel-Fuse-SFP.patch 2024-08-23 17:18:09.640429826 +0100 @@ -1 +1 @@ -From 3abfda0f7d58b2eef20cdf8e102825678b150421 Mon Sep 17 00:00:00 2001 +From 8d53ecbbf62d7a7496283a7572d5f3de1bcfe36d Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 3abfda0f7d58b2eef20cdf8e102825678b150421 ] + @@ -13 +14,0 @@ -Cc: stable@dpdk.org @@ -22 +23 @@ -index 54fe9faae0..ee9dcbe3da 100644 +index df334749e9..a458722e2e 100644 @@ -25 +26 @@ -@@ -579,4 +579,7 @@ static bool axgbe_phy_belfuse_parse_quirks(struct axgbe_port *pdata) +@@ -578,4 +578,7 @@ static bool axgbe_phy_belfuse_parse_quirks(struct axgbe_port *pdata)