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 2650A45DB9 for ; Wed, 27 Nov 2024 18:20:39 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1FD95402DE; Wed, 27 Nov 2024 18:20:39 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 4D0A3402DE for ; Wed, 27 Nov 2024 18:20:37 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1732728036; 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=qapHmBY82JHFQytdPdP2+WIo8VVxWjH9+m+AnQNbBa8=; b=Du5X63T+Nt55tIGMJAqjFTxwpT7txPmIqhEAGGcPygHUhIMFTzel9jNl46WyceuVN4HKez 1v0OqEFwW5f+cj0hE4izEf/zP1sHy66PGAIYTc2JpWU3uT988K4v8Ntw2INotO70fQxFHY dVAjFvQ0xwwtdMB3haJ2tzJPQM+LitU= Received: from mx-prod-mc-05.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-594-yJPEvV4OMM2r_xLk0zoJ0w-1; Wed, 27 Nov 2024 12:20:33 -0500 X-MC-Unique: yJPEvV4OMM2r_xLk0zoJ0w-1 X-Mimecast-MFC-AGG-ID: yJPEvV4OMM2r_xLk0zoJ0w Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (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-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 816721956080; Wed, 27 Nov 2024 17:20:32 +0000 (UTC) Received: from rh.redhat.com (unknown [10.39.192.52]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id C091030001A2; Wed, 27 Nov 2024 17:20:30 +0000 (UTC) From: Kevin Traynor To: Paul Greenwalt Cc: Soumyadeep Hore , Bruce Richardson , dpdk stable Subject: patch 'net/ice/base: fix link speed for 200G' has been queued to stable release 21.11.9 Date: Wed, 27 Nov 2024 17:17:36 +0000 Message-ID: <20241127171916.690404-29-ktraynor@redhat.com> In-Reply-To: <20241127171916.690404-1-ktraynor@redhat.com> References: <20241127171916.690404-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: NjG_gXmKIDV4Aq5FOa5ueam9Sb8yfO1uamtBRXMHTQc_1732728032 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.9 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 12/02/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/eca65c3d3f4dc4879e04676e1d5a3ce654884e43 Thanks. Kevin --- >From eca65c3d3f4dc4879e04676e1d5a3ce654884e43 Mon Sep 17 00:00:00 2001 From: Paul Greenwalt Date: Fri, 23 Aug 2024 09:56:45 +0000 Subject: [PATCH] net/ice/base: fix link speed for 200G [ upstream commit e3992ab377d2879d6c5bfb220865638404b85dba ] When setting PHY configuration during driver initialization, 200G link speed is not being advertised even when the PHY is capable. This is because the get PHY capabilities link speed response is being masked by ICE_AQ_LINK_SPEED_M, which does not include 200G link speed bit. Fixes: d13ad9cf1721 ("net/ice/base: add helper functions for PHY caching") Signed-off-by: Paul Greenwalt Signed-off-by: Soumyadeep Hore Acked-by: Bruce Richardson --- drivers/net/ice/base/ice_adminq_cmd.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ice/base/ice_adminq_cmd.h b/drivers/net/ice/base/ice_adminq_cmd.h index 2bf322610b..910665f26c 100644 --- a/drivers/net/ice/base/ice_adminq_cmd.h +++ b/drivers/net/ice/base/ice_adminq_cmd.h @@ -1575,5 +1575,5 @@ struct ice_aqc_get_link_status_data { #define ICE_AQ_LINK_PWR_QSFP_CLASS_4 3 __le16 link_speed; -#define ICE_AQ_LINK_SPEED_M 0x7FF +#define ICE_AQ_LINK_SPEED_M 0xFFF #define ICE_AQ_LINK_SPEED_10MB BIT(0) #define ICE_AQ_LINK_SPEED_100MB BIT(1) -- 2.47.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2024-11-27 17:17:39.210576044 +0000 +++ 0029-net-ice-base-fix-link-speed-for-200G.patch 2024-11-27 17:17:38.186269171 +0000 @@ -1 +1 @@ -From e3992ab377d2879d6c5bfb220865638404b85dba Mon Sep 17 00:00:00 2001 +From eca65c3d3f4dc4879e04676e1d5a3ce654884e43 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit e3992ab377d2879d6c5bfb220865638404b85dba ] + @@ -12 +13,0 @@ -Cc: stable@dpdk.org @@ -22 +23 @@ -index 6a89e1614a..3ec207927b 100644 +index 2bf322610b..910665f26c 100644 @@ -25 +26 @@ -@@ -1625,5 +1625,5 @@ struct ice_aqc_get_link_status_data { +@@ -1575,5 +1575,5 @@ struct ice_aqc_get_link_status_data {