From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Cc: <ajit.khaparde@broadcom.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 8/8] net/bnxt: fix the check for autoneg enablement in the PHY FW
Date: Thu, 16 Jun 2022 18:04:00 +0100 [thread overview]
Message-ID: <46814c8c-b354-3a7e-24a8-6087a06712b4@xilinx.com> (raw)
In-Reply-To: <20220615145703.6613-9-kalesh-anakkur.purayil@broadcom.com>
On 6/15/2022 3:57 PM, Kalesh A P wrote:
>
> From: Somnath Kotur<somnath.kotur@broadcom.com>
>
> The current combination of checks to determine whether autoneg is
> enabled in the card is a bit convoluted and may become incorrect
> as well in the future as one of the fields being used - auto_link_speed
> might become deprecated.
> Switch to using the 'auto_mode' field obtained from the response of
> HWRM_PHY_QCFG cmd as that is always deterministically set by the PHY
> FW.
> Fixed a bug in the 40G check to only look for the bit setting and
> not the actual value.
> Also, check the forced speeds first before trying to enforce the
> auto speeds
>
> Allow the user to set autoneg speed in all cases except for PAM4 200G
> as PAM4 200G will come up only in forced mode.
>
> Fixes: c23f9ded0391 ("net/bnxt: support 200G PAM4 link")
Is stable tag (stable@dpdk.org) omitted explicitly?
next prev parent reply other threads:[~2022-06-16 17:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 14:56 [dpdk-dev] [PATCH 0/8] bnxt PMD fixes Kalesh A P
2022-06-15 14:56 ` [dpdk-dev] [PATCH 1/8] net/bnxt: remove assert for zero data len in Tx path Kalesh A P
2022-06-16 17:03 ` Ferruh Yigit
2022-06-19 23:09 ` Ajit Khaparde
2022-06-20 10:55 ` Ferruh Yigit
2022-06-20 17:03 ` Ajit Khaparde
2022-06-15 14:56 ` [dpdk-dev] [PATCH 2/8] net/bnxt: fix switch domain allocation Kalesh A P
2022-06-15 14:56 ` [dpdk-dev] [PATCH 3/8] net/bnxt: reduce the verbosity of a log Kalesh A P
2022-06-15 14:56 ` [dpdk-dev] [PATCH 4/8] net/bnxt: allow Tx only or Rx only configs in PMD Kalesh A P
2022-06-16 17:03 ` Ferruh Yigit
2022-06-21 4:46 ` Kalesh Anakkur Purayil
2022-06-21 4:54 ` Damodharam Ammepalli
2022-06-21 7:57 ` Ferruh Yigit
2022-06-15 14:57 ` [dpdk-dev] [PATCH 5/8] net/bnxt: fix setting forced speed Kalesh A P
2022-06-15 14:57 ` [dpdk-dev] [PATCH 6/8] net/bnxt: disallow MTU change when device is started Kalesh A P
2022-06-15 14:57 ` [dpdk-dev] [PATCH 7/8] net/bnxt: cleanups in MTU set callback Kalesh A P
2022-06-15 14:57 ` [dpdk-dev] [PATCH 8/8] net/bnxt: fix the check for autoneg enablement in the PHY FW Kalesh A P
2022-06-16 17:04 ` Ferruh Yigit [this message]
2022-06-19 23:11 ` Ajit Khaparde
2022-06-26 20:45 ` [dpdk-dev] [PATCH 0/8] bnxt PMD fixes Ajit Khaparde
2022-06-27 2:08 ` Thomas Monjalon
2022-06-27 3:28 ` Ajit Khaparde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46814c8c-b354-3a7e-24a8-6087a06712b4@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=kalesh-anakkur.purayil@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).