DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Somnath Kotur <somnath.kotur@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>,
	Charlie Brtee <cfb@hpe.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [PATCH] net/bnxt: fix autoneg on PAM4 links
Date: Wed, 17 Nov 2021 20:55:23 -0800	[thread overview]
Message-ID: <CACZ4nhu5LPR0cFcPdVdy_Cu5Htdq25GLzGuVCDxLHZapLZ1ohg@mail.gmail.com> (raw)
In-Reply-To: <20211118040439.24583-1-somnath.kotur@broadcom.com>

On Wed, Nov 17, 2021 at 8:11 PM Somnath Kotur
<somnath.kotur@broadcom.com> wrote:
>
> If autonegotiation was enabled, driver was not passing the
> 'auto_pam4_link_speeds' obtained during init and stored in bp->link_info
> to bnxt_hwrm_port_phy_cfg(). This would result in an incorrect setting
> being passed to the HW during PHY configuration. This in turn, would
> result in invalid settings being retrieved and configured in subsequent
> application loads resulting in launch failures.
>
> Fixes: c23f9ded0391 ("net/bnxt: support 200G PAM4 link")
>
> Reported-by: Charlie Brtee <cfb@hpe.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com>
Merged in dpdk-next-net-brcm.

Fixed up typo in Charle's name.
Added Bugzilla ID and stable@dpdk.org

Thanks
Ajit

> ---
>  drivers/net/bnxt/bnxt_hwrm.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/bnxt/bnxt_hwrm.c b/drivers/net/bnxt/bnxt_hwrm.c
> index 67ed807dad..df75047e2d 100644
> --- a/drivers/net/bnxt/bnxt_hwrm.c
> +++ b/drivers/net/bnxt/bnxt_hwrm.c
> @@ -3247,6 +3247,8 @@ int bnxt_set_hwrm_link_config(struct bnxt *bp, bool link_up)
>                 link_req.auto_link_speed_mask =
>                         bnxt_parse_eth_link_speed_mask(bp,
>                                                        dev_conf->link_speeds);
> +               link_req.auto_pam4_link_speeds =
> +                       bp->link_info->auto_pam4_link_speeds;
>         } else {
>                 if (bp->link_info->phy_type ==
>                     HWRM_PORT_PHY_QCFG_OUTPUT_PHY_TYPE_BASET ||
> --
> 2.28.0.497.g54e85e7
>

      reply	other threads:[~2021-11-18  4:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18  4:04 Somnath Kotur
2021-11-18  4:55 ` Ajit Khaparde [this message]

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=CACZ4nhu5LPR0cFcPdVdy_Cu5Htdq25GLzGuVCDxLHZapLZ1ohg@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=cfb@hpe.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    /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).