From: Simon Horman <horms@kernel.org>
To: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
netdev@vger.kernel.org, jiri@nvidia.com,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>,
Piotr Kwapulinski <piotr.kwapulinski@intel.com>,
Stefan Wegrzyn <stefan.wegrzyn@intel.com>
Subject: Re: [PATCH iwl-next v5 12/15] ixgbe: add support for devlink reload
Date: Thu, 6 Mar 2025 09:41:13 +0000 [thread overview]
Message-ID: <20250306093854.GQ3666230@kernel.org> (raw)
In-Reply-To: <20250221115116.169158-13-jedrzej.jagielski@intel.com>
On Fri, Feb 21, 2025 at 12:51:13PM +0100, Jedrzej Jagielski wrote:
> The E610 adapters contain an embedded chip with firmware which can be
> updated using devlink flash. The firmware which runs on this chip is
> referred to as the Embedded Management Processor firmware (EMP
> firmware).
>
> Activating the new firmware image currently requires that the system be
> rebooted. This is not ideal as rebooting the system can cause unwanted
> downtime.
>
> The EMP firmware itself can be reloaded by issuing a special update
> to the device called an Embedded Management Processor reset (EMP
> reset). This reset causes the device to reset and reload the EMP
> firmware.
>
> Implement support for devlink reload with the "fw_activate" flag. This
> allows user space to request the firmware be activated immediately.
>
> Reviewed-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
> Co-developed-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> Co-developed-by: Piotr Kwapulinski <piotr.kwapulinski@intel.com>
> Signed-off-by: Piotr Kwapulinski <piotr.kwapulinski@intel.com>
> Co-developed-by: Stefan Wegrzyn <stefan.wegrzyn@intel.com>
> Signed-off-by: Stefan Wegrzyn <stefan.wegrzyn@intel.com>
> Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
...
> diff --git a/Documentation/networking/devlink/ixgbe.rst b/Documentation/networking/devlink/ixgbe.rst
> index 41aedf4b8017..e5fef951c6f5 100644
> --- a/Documentation/networking/devlink/ixgbe.rst
> +++ b/Documentation/networking/devlink/ixgbe.rst
> @@ -88,3 +88,18 @@ combined flash image that contains the ``fw.mgmt``, ``fw.undi``, and
> and device serial number. It is expected that this combination be used with an
> image customized for the specific device.
>
> +Reload
> +======
> +
> +The ``ixgbe`` driver supports activating new firmware after a flash update
> +using ``DEVLINK_CMD_RELOAD`` with the ``DEVLINK_RELOAD_ACTION_FW_ACTIVATE``
> +action.
> +
> +.. code:: shell
> + $ devlink dev reload pci/0000:01:00.0 reload action fw_activate
> +The new firmware is activated by issuing a device specific Embedded
> +Management Processor reset which requests the device to reset and reload the
> +EMP firmware image.
> +
> +The driver does not currently support reloading the driver via
> +``DEVLINK_RELOAD_ACTION_DRIVER_REINIT``.
Hi Jedrzej, all,
This is not a proper review. And I didn't look into this, but make htmldocs
complains that:
.../ixgbe.rst:98: ERROR: Error in "code" directive:
maximum 1 argument(s) allowed, 9 supplied.
.. code:: shell
$ devlink dev reload pci/0000:01:00.0 reload action fw_activate
...
next prev parent reply other threads:[~2025-03-06 9:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 11:51 [PATCH iwl-next v5 00/15] ixgbe: Add basic devlink support Jedrzej Jagielski
2025-02-21 11:51 ` [PATCH iwl-next v5 01/15] devlink: add value check to devlink_info_version_put() Jedrzej Jagielski
2025-03-03 11:43 ` [Intel-wired-lan] " R, Bharath
2025-03-03 16:22 ` Kalesh Anakkur Purayil
2025-02-21 11:51 ` [PATCH iwl-next v5 02/15] ixgbe: wrap netdev_priv() usage Jedrzej Jagielski
2025-02-21 11:51 ` [PATCH iwl-next v5 03/15] ixgbe: add initial devlink support Jedrzej Jagielski
2025-03-03 8:24 ` [Intel-wired-lan] " R, Bharath
2025-02-21 11:51 ` [PATCH iwl-next v5 04/15] ixgbe: add handler for devlink .info_get() Jedrzej Jagielski
2025-02-21 11:51 ` [PATCH iwl-next v5 05/15] ixgbe: add E610 functions for acquiring flash data Jedrzej Jagielski
2025-03-03 11:44 ` [Intel-wired-lan] " R, Bharath
2025-02-21 11:51 ` [PATCH iwl-next v5 06/15] ixgbe: read the OROM version information Jedrzej Jagielski
2025-02-21 11:51 ` [PATCH iwl-next v5 07/15] ixgbe: read the netlist " Jedrzej Jagielski
2025-03-03 11:12 ` [Intel-wired-lan] " R, Bharath
2025-02-21 11:51 ` [PATCH iwl-next v5 08/15] ixgbe: add .info_get extension specific for E610 devices Jedrzej Jagielski
2025-02-21 11:51 ` [PATCH iwl-next v5 09/15] ixgbe: add E610 functions getting PBA and FW ver info Jedrzej Jagielski
2025-03-04 8:31 ` [Intel-wired-lan] " R, Bharath
2025-02-21 11:51 ` [PATCH iwl-next v5 10/15] ixgbe: extend .info_get with stored versions Jedrzej Jagielski
2025-02-21 11:51 ` [PATCH iwl-next v5 11/15] ixgbe: add device flash update via devlink Jedrzej Jagielski
2025-03-03 8:20 ` [Intel-wired-lan] " R, Bharath
2025-02-21 11:51 ` [PATCH iwl-next v5 12/15] ixgbe: add support for devlink reload Jedrzej Jagielski
2025-03-03 8:17 ` [Intel-wired-lan] " R, Bharath
2025-03-06 9:41 ` Simon Horman [this message]
2025-03-06 13:33 ` Jagielski, Jedrzej
2025-02-21 11:51 ` [PATCH iwl-next v5 13/15] ixgbe: add FW API version check Jedrzej Jagielski
2025-02-21 11:51 ` [PATCH iwl-next v5 14/15] ixgbe: add E610 implementation of FW recovery mode Jedrzej Jagielski
2025-02-21 11:51 ` [PATCH iwl-next v5 15/15] ixgbe: add support for FW rollback mode Jedrzej Jagielski
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=20250306093854.GQ3666230@kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jedrzej.jagielski@intel.com \
--cc=jiri@nvidia.com \
--cc=mateusz.polchlopek@intel.com \
--cc=netdev@vger.kernel.org \
--cc=piotr.kwapulinski@intel.com \
--cc=slawomirx.mrozowicz@intel.com \
--cc=stefan.wegrzyn@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).