From: Jacob Keller <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [net-next 0/4] ice: miscellaneous firmware features
Date: Wed, 8 Sep 2021 16:49:20 -0700 [thread overview]
Message-ID: <20210908234924.3416592-1-jacob.e.keller@intel.com> (raw)
This series contains a few miscellaneous left over pieces of work related to
flash update that I've been meaning to submit for a while.
This includes the following:
* a new shadow-ram region similar to NVM region but for the device shadow
RAM contents. This is distinct from NVM region because shadow RAM is
built up during device init and may be different from the raw NVM flash
data. (As I found out while debugging some issues with flash update).
* refactoring of the ice_flash_pldm_image to become the main flash update
entry point. This is simpler than having both a ice_devlink_flash_update
and an ice_flash_pldm_image. It will make additions like dry-run easier
in the future
* support for firmware activation via devlink reload, when possible.
The major new work is the reload support, which allows activating firmware
immediately without a reboot when possible.
As a note, I want to call out that the reload support here only supports
firmware activation. I really did try to see what it would take to get
proper driver reload support working. Unfortunately this task requires a
large amount of rewrite to the entire flow that the driver uses for both
probe/remove, as well as driver reset.
Jacob Keller (4):
ice: devlink: add shadow-ram region to snapshot Shadow RAM
ice: move and rename ice_check_for_pending_update
ice: refactor ice_flash_pldm_image and combine with
ice_devlink_flash_update
ice: support immediate firmware activation via devlink reload
drivers/net/ethernet/intel/ice/ice.h | 9 +
.../net/ethernet/intel/ice/ice_adminq_cmd.h | 7 +
drivers/net/ethernet/intel/ice/ice_common.c | 12 +
drivers/net/ethernet/intel/ice/ice_devlink.c | 218 ++++++++++---
.../net/ethernet/intel/ice/ice_fw_update.c | 291 ++++++++++++------
.../net/ethernet/intel/ice/ice_fw_update.h | 9 +-
drivers/net/ethernet/intel/ice/ice_type.h | 4 +
7 files changed, 412 insertions(+), 138 deletions(-)
base-commit: 8945c4bc5e8e03b2358974e602dcf8137b448ed9
--
2.31.1.331.gb0c09ab8796f
next reply other threads:[~2021-09-08 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 23:49 Jacob Keller [this message]
2021-09-08 23:49 ` [Intel-wired-lan] [net-next 1/4] ice: devlink: add shadow-ram region to snapshot Shadow RAM Jacob Keller
2021-09-30 17:45 ` G, GurucharanX
2021-09-08 23:49 ` [Intel-wired-lan] [net-next 2/4] ice: move and rename ice_check_for_pending_update Jacob Keller
2021-09-27 17:40 ` G, GurucharanX
2021-09-08 23:49 ` [Intel-wired-lan] [net-next 3/4] ice: refactor ice_flash_pldm_image and combine with ice_devlink_flash_update Jacob Keller
2021-09-27 17:39 ` G, GurucharanX
2021-09-08 23:49 ` [Intel-wired-lan] [net-next 4/4] ice: support immediate firmware activation via devlink reload Jacob Keller
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=20210908234924.3416592-1-jacob.e.keller@intel.com \
--to=jacob.e.keller@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.