DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
	Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH v2 0/2] write link speed to control BAR
Date: Fri, 10 Mar 2023 14:25:40 +0800	[thread overview]
Message-ID: <20230310062542.817107-1-chaoyong.he@corigine.com> (raw)
In-Reply-To: <20230221062955.34210-1-chaoyong.he@corigine.com>

Due to changes in the firmware for NFPs, firmware will no longer write
the link speed of a port to the control BAR. In line with the behaviour
of the kernel NFP driver, this is now handled by the PMD by reading the
value provided by the NSP in the nfp_eth_table struct within the pf_dev
of the port and subsequently writing this value to the control BAR.

---
V2:
* Using the 16bit read/write helper functions
---
James Hershaw (2):
  net/nfp: add helper functions for read/write 16b values
  net/nfp: write link speed to control BAR

 drivers/net/nfp/nfp_common.c | 104 +++++++++++++++++++++++------------
 drivers/net/nfp/nfp_common.h |  17 ++++++
 drivers/net/nfp/nfp_ctrl.h   |   9 +++
 3 files changed, 94 insertions(+), 36 deletions(-)

-- 
2.39.1


  parent reply	other threads:[~2023-03-10  6:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21  6:29 [PATCH] net/nfp: " Chaoyong He
2023-02-23 16:39 ` Ferruh Yigit
2023-03-06  7:06   ` Chaoyong He
2023-03-07 13:24     ` Ferruh Yigit
2023-03-10  6:07       ` Chaoyong He
2023-03-10  6:25 ` Chaoyong He [this message]
2023-03-10  6:25   ` [PATCH v2 1/2] net/nfp: add helper functions for read/write 16b values Chaoyong He
2023-03-10  6:25   ` [PATCH v2 2/2] net/nfp: write link speed to control BAR Chaoyong He
2023-03-10 11:15     ` Ferruh Yigit
2023-03-13  3:03       ` Chaoyong He
2023-03-13  8:39         ` Ferruh Yigit
2023-03-13 10:18   ` [PATCH v2 0/2] " 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=20230310062542.817107-1-chaoyong.he@corigine.com \
    --to=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=niklas.soderlund@corigine.com \
    --cc=oss-drivers@corigine.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).