From: David Miller <davem@davemloft.net>
To: simon.horman@netronome.com
Cc: jakub.kicinski@netronome.com, netdev@vger.kernel.org,
oss-drivers@netronome.com, dirk.vandermerwe@netronome.com
Subject: Re: [PATCH net-next v2 00/11] nfp: implement firmware loading policy
Date: Tue, 10 Sep 2019 18:30:35 +0200 (CEST) [thread overview]
Message-ID: <20190910.183035.1659598063632819738.davem@davemloft.net> (raw)
In-Reply-To: <20190908235427.9757-1-simon.horman@netronome.com>
From: Simon Horman <simon.horman@netronome.com>
Date: Mon, 9 Sep 2019 00:54:16 +0100
> Dirk says:
>
> This series adds configuration capabilities to the firmware loading policy of
> the NFP driver.
>
> NFP firmware loading is controlled via three HWinfo keys which can be set per
> device: 'abi_drv_reset', 'abi_drv_load_ifc' and 'app_fw_from_flash'.
> Refer to patch #11 for more detail on how these control the firmware loading.
>
> In order to configure the full extend of FW loading policy, a new devlink
> parameter has been introduced, 'reset_dev_on_drv_probe', which controls if the
> driver should reset the device when it's probed. This, in conjunction with the
> existing 'fw_load_policy' (extended to include a 'disk' option) provides the
> means to tweak the NFP HWinfo keys as required by users.
>
> Patches 1 and 2 adds the devlink modifications and patches 3 through 9 adds the
> support into the NFP driver. Furthermore, the last 2 patches are documentation
> only.
>
> v2:
> Renamed all 'reset_dev_on_drv_probe' defines the same as the devlink parameter
> name (Jiri)
Series applied, thanks Simon.
prev parent reply other threads:[~2019-09-10 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 23:54 [PATCH net-next v2 00/11] nfp: implement firmware loading policy Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 01/11] devlink: extend 'fw_load_policy' values Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 02/11] devlink: add 'reset_dev_on_drv_probe' param Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 03/11] nfp: nsp: add support for fw_loaded command Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 04/11] nfp: nsp: add support for optional hwinfo lookup Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 05/11] nfp: nsp: add support for hwinfo set operation Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 06/11] nfp: honor FW reset and loading policies Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 07/11] nfp: add devlink param infrastructure Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 08/11] nfp: devlink: add 'fw_load_policy' support Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 09/11] nfp: devlink: add 'reset_dev_on_drv_probe' support Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 10/11] kdoc: fix nfp_fw_load documentation Simon Horman
2019-09-08 23:54 ` [PATCH net-next v2 11/11] Documentation: nfp: add nfp driver specific notes Simon Horman
2019-09-10 16:30 ` David Miller [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=20190910.183035.1659598063632819738.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dirk.vandermerwe@netronome.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=simon.horman@netronome.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).