From: Chaoyong He <chaoyong.he@corigine.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: oss-drivers <oss-drivers@corigine.com>,
Nole Zhang <peng.zhang@corigine.com>
Subject: RE: [PATCH 3/3] net/nfp: add force reload firmware option
Date: Fri, 1 Mar 2024 02:06:40 +0000 [thread overview]
Message-ID: <SJ0PR13MB5545F6349535C1C145479F049E5E2@SJ0PR13MB5545.namprd13.prod.outlook.com> (raw)
In-Reply-To: <18e73137-63aa-4760-84cc-3e3b16601ba3@amd.com>
> On 2/27/2024 11:15 AM, Chaoyong He wrote:
> > From: Peng Zhang <peng.zhang@corigine.com>
> >
> > Add an option to force reload the firmware.
> >
> > This option can be ignored in some case, for example:
> > When using a 2 port NFP card and both with this reload firmware
> > option, only the first one will cause the firmware reload and the
> > second one will be ignored.
> >
> > Signed-off-by: Peng Zhang <peng.zhang@corigine.com>
> > Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> > ---
> > drivers/net/nfp/nfp_ethdev.c | 104 +++++++++++++++++++++++++++--
> --
> > drivers/net/nfp/nfp_net_common.h | 8 +++
> > 2 files changed, 100 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/net/nfp/nfp_ethdev.c
> > b/drivers/net/nfp/nfp_ethdev.c index 902a62a86b..8c38b4e134 100644
> > --- a/drivers/net/nfp/nfp_ethdev.c
> > +++ b/drivers/net/nfp/nfp_ethdev.c
> > @@ -9,6 +9,7 @@
> >
> > #include <eal_firmware.h>
> > #include <rte_alarm.h>
> > +#include <rte_kvargs.h>
> >
> > #include "flower/nfp_flower.h"
> > #include "nfd3/nfp_nfd3.h"
> > @@ -31,6 +32,71 @@
> > #define NFP_NET_APP_CAP_SP_INDIFF RTE_BIT64(0) /* Indifferent to
> port speed */
> >
> > #define NFP_PF_DRIVER_NAME net_nfp_pf
> > +#define NFP_PF_FORCE_RELOAD_FW "force_reload_fw"
> > +
> >
>
> Can you please document the new devarg in the driver documentation,
> 'doc/guides/nics/nfp.rst'?
>
> Also you may want to document FW upgrade process, as it checks FW version
> by default and this can be overridden by devarg etc..
Okay, we will document it in the next version patch series, thanks.
next prev parent reply other threads:[~2024-03-01 2:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 11:15 [PATCH 0/3] reload the firmware as needed Chaoyong He
2024-02-27 11:15 ` [PATCH 1/3] net/nfp: add the elf module Chaoyong He
2024-02-28 16:50 ` Ferruh Yigit
2024-03-01 2:38 ` Chaoyong He
2024-02-28 22:18 ` Stephen Hemminger
2024-03-01 17:22 ` Ferruh Yigit
2024-03-04 1:13 ` Chaoyong He
2024-03-04 8:50 ` Ferruh Yigit
2024-02-27 11:15 ` [PATCH 2/3] net/nfp: reload the firmware only when firmware changed Chaoyong He
2024-02-27 11:15 ` [PATCH 3/3] net/nfp: add force reload firmware option Chaoyong He
2024-02-28 16:53 ` Ferruh Yigit
2024-03-01 2:06 ` Chaoyong He [this message]
2024-03-01 8:42 ` [PATCH v2 0/3] reload the firmware as needed Chaoyong He
2024-03-01 8:42 ` [PATCH v2 1/3] net/nfp: add the elf module Chaoyong He
2024-03-01 8:42 ` [PATCH v2 2/3] net/nfp: reload the firmware only when firmware changed Chaoyong He
2024-03-01 8:42 ` [PATCH v2 3/3] net/nfp: add force reload firmware option Chaoyong He
2024-03-04 13:28 ` [PATCH v2 0/3] reload the firmware as needed 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=SJ0PR13MB5545F6349535C1C145479F049E5E2@SJ0PR13MB5545.namprd13.prod.outlook.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=oss-drivers@corigine.com \
--cc=peng.zhang@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).