update_drv_state(9)

💖 NAME 💖

update_drv_state — the API that literally just tells everyone "hey bestie, the driver state changed" ✨

okay so quick vibe check: this is from the Kernel API Manual, section 9, and it's giving "small function, big responsibilities." 🎀

---

🌸 SYNOPSIS 🌸

int update_drv_state (struct qed_dev *cdev , bool active );

like, that's the whole thing. short king energy 👑

---

🦋 ARGUMENTS 🦋

• cdev — the Qed dev pointer. it's the device we're talking about, the main character of this whole operation 💅
• active — active. yes bestie, that's the whole description. it's a bool, it's active, we move 🫶

---

⭐ RETURN ⭐

Returns an Int. that's it. that's the return value. ngl the docs are being mysterious on purpose here 😭

---

🧚 SEE ALSO 🧚

first up, the kernel file, no cap:

./include/linux/qed/qed_if.h

and then the whole friend group — this function does not run alone, it's a whole squad 🔥:

• selftest_interrupt(9)
• selftest_memory(9)
• selftest_register(9)
• selftest_clock(9)
• selftest_nvram(9)
• can_link_change(9)
• set_link(9)
• get_link(9)
• drain(9)
• update_msglvl(9)
• nvm_flash(9)
• nvm_get_image(9)
• set_coalesce(9)
• set_led(9)
• attn_clr_enable(9)
• db_recovery_add(9)
• db_recovery_del(9)
• recovery_process(9)
• recovery_prolog(9)
• update_mac(9)
• update_mtu(9)
• update_wol(9)
• read_module_eeprom(9)
• get_affin_hwfn_idx(9)
• read_nvm_cfg(9)
• read_nvm_cfg_len(9)
• set_grc_config(9)
• qed_sb_ack(9)

28 entries, all accounted for, we don't skip a single one in this house 😤💜

lowkey a reminder: this page only lists these as see also — it's not claiming anything extra about what they do. iykyk 💀

---

and that's the page bestie!! 🌈 written up from ./include/linux/qed, dated October 2026, and closed out with update_drv_state(9) right where it belongs. periodt 💅✨