mpi3mr_cfg_get_sas_phy_pg0(9)

📦 version 7.3.1, in nixpkgs unstable

💖 mpi3mr_cfg_get_sas_phy_pg0 — read current SAS Phy page0 💖

okay bestie, welcome to the Kernel API Manual page for mpi3mr_cfg_get_sas_phy_pg0(9). yes that's a whole mouthful, but it's lowkey iconic — this is the little handler that goes and reads the current SAS Phy page0 for you. let's get into it ✨

🎀 SYNOPSIS 🎀

int mpi3mr_cfg_get_sas_phy_pg0 (struct mpi3mr_ioc *mrioc , u16
*ioc_status , struct mpi3_sas_phy_page0 *phy_pg0 , u16 pg_sz , u32 form
, u32 form_spec );

🌸 ARGUMENTS 🌸

  • mrioc — the adapter instance reference, aka your main character. it's the controller you're talking to 💅
  • ioc_status — pointer to return the ioc status in. this is where the controller's own status comes back to you, so pay attention
  • phy_pg0 — pointer to return SAS Phy page 0. this is the whole point of the function, bestie 🦋
  • pg_sz — size of the memory allocated to the page pointer. so like, how much room you actually gave it
  • form — the form to be used for addressing the page 🎀
  • form_spec — form specific information, like the phy number. it's giving "details that depend on which form you picked" ✨

💜 DESCRIPTION 💜

so this is the handler for config page read for a specific SAS Phy page0. slay.

the ioc_status has the controller returned ioc_status — fr, that's where it lands.

⚠️ huge heads up bestie: this routine doesn't check ioc_status to decide whether the page read is a success or not. and it's the caller's responsibility. so like, the function is not gonna hold your hand and tell you if it worked — you gotta check that yourself, no cap 😭

🫶 RETURN 🫶

  • 0 on success
  • non-zero on failure

periodt. 👑

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/mpi3mr/mpi3mr_fw.c — and the whole friend group of related functions, all together, all accounted for, not one skipped 💖:

and that's the whole page bb 🧚💜 this lil beauty lives over in ./drivers/scsi/mpi3mr, dated October 2026 — go read it, it ate 💅✨

📦 where this page comes from