bnxt_en: Add missing 200G link speed reporting
[ Upstream commit 581bce7bcb7e7f100908728e7b292e266c76895b ]
bnxt_fw_to_ethtool_speed() is missing the case statement for 200G
link speed reported by firmware. As a result, ethtool will report
unknown speed when the firmware reports 200G link speed.
Fixes: 532262ba3b
("bnxt_en: ethtool: support PAM4 link speeds up to 200G")
Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:

committed by
Greg Kroah-Hartman

parent
62850a0763
commit
8104c79551
@@ -1198,6 +1198,7 @@ struct bnxt_link_info {
|
|||||||
#define BNXT_LINK_SPEED_40GB PORT_PHY_QCFG_RESP_LINK_SPEED_40GB
|
#define BNXT_LINK_SPEED_40GB PORT_PHY_QCFG_RESP_LINK_SPEED_40GB
|
||||||
#define BNXT_LINK_SPEED_50GB PORT_PHY_QCFG_RESP_LINK_SPEED_50GB
|
#define BNXT_LINK_SPEED_50GB PORT_PHY_QCFG_RESP_LINK_SPEED_50GB
|
||||||
#define BNXT_LINK_SPEED_100GB PORT_PHY_QCFG_RESP_LINK_SPEED_100GB
|
#define BNXT_LINK_SPEED_100GB PORT_PHY_QCFG_RESP_LINK_SPEED_100GB
|
||||||
|
#define BNXT_LINK_SPEED_200GB PORT_PHY_QCFG_RESP_LINK_SPEED_200GB
|
||||||
u16 support_speeds;
|
u16 support_speeds;
|
||||||
u16 support_pam4_speeds;
|
u16 support_pam4_speeds;
|
||||||
u16 auto_link_speeds; /* fw adv setting */
|
u16 auto_link_speeds; /* fw adv setting */
|
||||||
|
@@ -1653,6 +1653,8 @@ u32 bnxt_fw_to_ethtool_speed(u16 fw_link_speed)
|
|||||||
return SPEED_50000;
|
return SPEED_50000;
|
||||||
case BNXT_LINK_SPEED_100GB:
|
case BNXT_LINK_SPEED_100GB:
|
||||||
return SPEED_100000;
|
return SPEED_100000;
|
||||||
|
case BNXT_LINK_SPEED_200GB:
|
||||||
|
return SPEED_200000;
|
||||||
default:
|
default:
|
||||||
return SPEED_UNKNOWN;
|
return SPEED_UNKNOWN;
|
||||||
}
|
}
|
||||||
|
Reference in New Issue
Block a user