DPDK patches and discussions
 help / color / mirror / Atom feed
From: <ssebasti@amd.com>
To: <dev@dpdk.org>
Cc: <chandu@amd.com>, <ferruh.yigit@intel.com>
Subject: [PATCH v1 2/2] net/axgbe: disable the CDR wa for Yellow Carp devices
Date: Mon, 31 Jan 2022 11:09:20 +0530	[thread overview]
Message-ID: <20220131053920.167230-3-ssebasti@amd.com> (raw)
In-Reply-To: <20220131053920.167230-1-ssebasti@amd.com>

From: Selwin Sebastian <selwin.sebastian@amd.com>

Yellow Carp ethernet devices (V3xxx) do not require
autonegotiation CDR workaround, hence disable the same.

Signed-off-by: Selwin Sebastian <selwin.sebastian@amd.com>
---
 drivers/net/axgbe/axgbe_ethdev.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/net/axgbe/axgbe_ethdev.c b/drivers/net/axgbe/axgbe_ethdev.c
index 2be9387f98..951da5cc26 100644
--- a/drivers/net/axgbe/axgbe_ethdev.c
+++ b/drivers/net/axgbe/axgbe_ethdev.c
@@ -2205,6 +2205,8 @@ eth_axgbe_dev_init(struct rte_eth_dev *eth_dev)
 	case AMD_PCI_YC_ROOT_COMPLEX_ID:
 		pdata->xpcs_window_def_reg = PCS_V2_YC_WINDOW_DEF;
 		pdata->xpcs_window_sel_reg = PCS_V2_YC_WINDOW_SELECT;
+		/* Yellow Carp devices do not need cdr workaround */
+		pdata->vdata->an_cdr_workaround = 0;
 		break;
 	case AMD_PCI_SNOWY_ROOT_COMPLEX_ID:
 		pdata->xpcs_window_def_reg = PCS_V2_WINDOW_DEF;
-- 
2.25.1


  parent reply	other threads:[~2022-01-31  5:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31  5:39 [PATCH v1 0/2] net/axgbe: Add support for Yellow Carp ethernet ssebasti
2022-01-31  5:39 ` [PATCH v1 1/2] net/axgbe: add support for Yellow Carp ethernet device ssebasti
2022-01-31  6:48   ` Namburu, Chandu-babu
2022-02-03 11:56     ` Ferruh Yigit
2022-02-01 14:26   ` Ferruh Yigit
2022-02-02  8:56     ` Sebastian, Selwin
2022-02-02 10:53       ` Ferruh Yigit
2022-02-02 11:56         ` Sebastian, Selwin
2022-01-31  5:39 ` ssebasti [this message]
2022-02-01 14:23 ` [PATCH v1 0/2] net/axgbe: Add support for Yellow Carp ethernet Ferruh Yigit

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=20220131053920.167230-3-ssebasti@amd.com \
    --to=ssebasti@amd.com \
    --cc=chandu@amd.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).