ice_write_one_nvm_block(9)

💖 ice_write_one_nvm_block(9) 💖

✨ NAME ✨

okay bestie, this page is ice_write_one_nvm_block(9) from the Kernel API Manual — and it's literally “Write an NVM block and await completion response.” 🎀

---

🦋 SYNOPSIS 🦋

int ice_write_one_nvm_block (struct ice_pf *pf , u16 module , u32 offset , u16 block_size , u8 *block , bool last_cmd , u8 *reset_level , struct netlink_ext_ack *extack );

🎀 ARGUMENTS 🎀

• pf — the PF data structure
• module — the module to write to
• offset — offset in bytes
• block_size — size of the block to write, up to 4k
• block — pointer to block of data to write
• last_cmd — whether this is the last command
• reset_level — storage for reset level required
• extack — netlink extended ACK structure

🌸 DESCRIPTION 🌸

okay so this function writes a block of data to a flash module, and then awaits for the completion response message from firmware. 💅

Important vibe check: this function assumes the caller has acquired the NVM resource. No cap.

On successful return, reset_level indicates the device reset required to complete the update. Here's the reset-level lore, bestie:

• 0 — ICE_AQC_NVM_POR_FLAG — A full power on is required
• 1 — ICE_AQC_NVM_PERST_FLAG — A cold PCIe reset is required
• 2 — ICE_AQC_NVM_EMPR_FLAG — An EMP reset is required

🌈 RETURN 🌈

zero on success, or a negative error code on failure.

👑 SEE ALSO 👑

• Kernel file ./drivers/net/ethernet/intel/ice/ice_fw_update.c
• ice_send_package_data(9)
• ice_check_component_response(9)
• ice_send_component_table(9)
• ice_write_nvm_module(9)
• ice_erase_nvm_module(9)
• ice_switch_flash_banks(9)
• ice_flash_component(9)
• ice_finalize_update(9)
• ice_op_pci_match_record(9)
• ice_get_pending_updates(9)
• ice_cancel_pending_update(9)
• ice_devlink_flash_update(9)

---

xoxo, source/version is ./drivers/net/ethernet/intel/ice, dated October 2026, signing off as ice_write_one_nvm_block(9) — catch you in the next page 💜