]> git.droids-corp.org - dpdk.git/commit
net/bnxt: fix setting forced speed
authorKalesh AP <kalesh-anakkur.purayil@broadcom.com>
Wed, 15 Jun 2022 14:57:00 +0000 (20:27 +0530)
committerAjit Khaparde <ajit.khaparde@broadcom.com>
Fri, 24 Jun 2022 21:24:08 +0000 (23:24 +0200)
commitd9ae3e9d53253418e2f9f97b19849c0a625159ed
tree05cf999cc1ee76634d5ad49aa15c69d5e0b1bc4d
parent8b7e58a791ef7747266b77ed433f5d03a6abaad7
net/bnxt: fix setting forced speed

The "active_fec_signal_mode" in HWRM_PORT_PHY_QCFG response
does not return correct value till the link is up. Driver cannot
rely on active_fec_signal_mode while setting forced speed.

While setting forced speed of 50G/100G/200G, check if PAM4 speeds
are supported for the port first and then populate the HWRM request
accordingly.

Also, If PAM4 speed is supported, use PAM4 supported speed while
reporting speed capabilities.

Fixes: c23f9ded0391 ("net/bnxt: support 200G PAM4 link")
Cc: stable@dpdk.org
Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
drivers/net/bnxt/bnxt_ethdev.c
drivers/net/bnxt/bnxt_hwrm.c
drivers/net/bnxt/bnxt_hwrm.h