lpfc_sli4_pd...tus_reg_wait(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

lpfc_sli4_pdev_status_reg_wait — wait for pdev status register for readiness.

okay so this is straight outta the Kernel API Manual, bestie. The page header title is lpfc_sli4_pd...tus_reg_wait(9), and the actual function name is lpfc_sli4_pdev_status_reg_wait. This is the “wait for pdev status register for readiness” situation, and yes it’s giving kernel-api main character energy. 💅

✨ SYNOPSIS ✨

int lpfc_sli4_pdev_status_reg_wait (struct lpfc_hba *phba );

🫶 ARGUMENTS 🫶

  • phba — an lpfc_hba pointer. That’s it, that’s the whole argument list, and honestly? iconic.

🦋 DESCRIPTION 🦋

This one is for the SLI4 interface type-2 device: you wait on the sliport status register for readiness after performing a firmware reset. no cap, that’s the whole job. It’s the “hold up, let the firmware reset happen, then check the status register for readiness” moment, and the vibe check is literally the register. 🦋

🔥 RETURN 🔥

  • 0 — zero for success. slay. 💅
  • -EPERM — returned when the port does not have privilege to perform the reset.
  • -EIO — returned when the port timeout from recovering from the reset. 😭

💀 NOTE 💀

⚠️ NOTE: As the caller will interpret the return code by value, be careful in making change or addition to return codes. This is the part where you do not freestyle new return codes, bestie. fr fr.

🌈 SEE ALSO 🌈

Kernel file: ./drivers/scsi/lpfc/lpfc_attr.c — that’s the source home for this whole crew. Here’s the full SEE ALSO friend group, every single ref exactly as written:

xoxo, kernel bestie 💅✨

footer energy: source/version ./drivers/scsi/lpfc · page tag lpfc_sli4_pd...tus_reg_wait(9) · date October 2026
📦 where this page comes from