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 C266945849; Fri, 23 Aug 2024 12:52:08 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 80D9643351; Fri, 23 Aug 2024 12:51:36 +0200 (CEST) Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.9]) by mails.dpdk.org (Postfix) with ESMTP id D4AF043332; Fri, 23 Aug 2024 12:51:34 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1724410295; x=1755946295; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=kI6OecT5j00wUgT0ybnawa+8dFewAdflkvnoUTEi5I4=; b=XCCjIPgngWHo8sSPe1ykrPvIMY/fz/8bX7+Vzze75b2IVooPV0lSjL+G j6hZ1skZj9TBXaHKwFvfAjew79c/l4rmgzZoQUEd856QlrUJdF1f0Ct/q Mg4OMqfxVsHJXVkxDCHa/nzu4Fi5c2fx78aM27ZQuQrKZfxRJgipBS+J6 c0NDhWRxaSm9IKMB7TDHQ66x/bmiBAPEIUYHM/JxSdwP7Dqk3uHJVx57x +KQDScwbdm+fqCzLGEMCh5ZjtwNXq+oq85AX1wT1bOVELuYZ6wY3OnCCi QEm2W3ctRzlofRm4+FZpcBUFoxLOac4Y6So/jxqGnhY8iX0oSeC/smj+Q w==; X-CSE-ConnectionGUID: sIkKA+rpRYWDiC9GcBEH1A== X-CSE-MsgGUID: 6ZGolaz4RZWudI3azz76Gw== X-IronPort-AV: E=McAfee;i="6700,10204,11172"; a="33535648" X-IronPort-AV: E=Sophos;i="6.10,170,1719903600"; d="scan'208";a="33535648" Received: from orviesa010.jf.intel.com ([10.64.159.150]) by fmvoesa103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Aug 2024 03:51:34 -0700 X-CSE-ConnectionGUID: wBvr/7icSSqol93ZvYouPQ== X-CSE-MsgGUID: QGQHkVCKRfSolgk2ezla2A== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.10,170,1719903600"; d="scan'208";a="61617719" Received: from unknown (HELO npf-hyd-clx-03..) ([10.145.170.182]) by orviesa010.jf.intel.com with ESMTP; 23 Aug 2024 03:51:32 -0700 From: Soumyadeep Hore To: bruce.richardson@intel.com, ian.stokes@intel.com, aman.deep.singh@intel.com Cc: dev@dpdk.org, shaiq.wani@intel.com, Paul Greenwalt , stable@dpdk.org Subject: [PATCH v3 07/12] net/ice: fix link speed for 200G Date: Fri, 23 Aug 2024 09:56:45 +0000 Message-ID: <20240823095650.349785-8-soumyadeep.hore@intel.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240823095650.349785-1-soumyadeep.hore@intel.com> References: <20240822185346.221885-13-soumyadeep.hore@intel.com> <20240823095650.349785-1-soumyadeep.hore@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org From: Paul Greenwalt 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") Cc: stable@dpdk.org Signed-off-by: Paul Greenwalt Signed-off-by: Soumyadeep Hore --- 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 6a89e1614a..3ec207927b 100644 --- a/drivers/net/ice/base/ice_adminq_cmd.h +++ b/drivers/net/ice/base/ice_adminq_cmd.h @@ -1624,7 +1624,7 @@ struct ice_aqc_get_link_status_data { #define ICE_AQ_LINK_PWR_QSFP_CLASS_3 2 #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) #define ICE_AQ_LINK_SPEED_1000MB BIT(2) -- 2.43.0