From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com
Subject: Re: [PATCH v2 0/2] write link speed to control BAR
Date: Mon, 13 Mar 2023 10:18:28 +0000 [thread overview]
Message-ID: <65b65271-eaaa-a4aa-72f9-aa3e69c39c81@amd.com> (raw)
In-Reply-To: <20230310062542.817107-1-chaoyong.he@corigine.com>
On 3/10/2023 6:25 AM, Chaoyong He wrote:
> 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
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-03-13 10:18 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 ` [PATCH v2 0/2] " Chaoyong He
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 ` Ferruh Yigit [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=65b65271-eaaa-a4aa-72f9-aa3e69c39c81@amd.com \
--to=ferruh.yigit@amd.com \
--cc=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).