mpi3mr_cfg_g..._io_unit_pg0(9)

📦 version 7.3.1, in nixpkgs unstable

💅 mpi3mr_cfg_get_sas_io_unit_pg0(9) 💅

okay so bestie, welcome to the kernel API manual for mpi3mr_cfg_get_sas_io_unit_pg0(9) — yes she's from the mpi3mr neck of the woods, yes that's the driver for those Broadcom-ish SAS tri-mode HBAs, and yes we're gonna get through this together 🫶

✨ NAME ✨

mpi3mr_cfg_get_sas_io_unit_pg0 — literally just reads the current SASIOUnit page0. that's the whole vibe. no cap 💖

🌸 SYNOPSIS 🌸

int mpi3mr_cfg_get_sas_io_unit_pg0 (struct mpi3mr_ioc *mrioc , struct
       mpi3_sas_io_unit_page0 *sas_io_unit_pg0 , u16 pg_sz );

🦋 ARGUMENTS 🦋

  • mrioc — the adapter instance reference. like, your actual controller, the main character of this whole operation 👑
  • sas_io_unit_pg0 — pointer to where the goods get returned: SAS IO Unit page 0, freshly hauled out of the firmware 🎀
  • pg_sz — size of the memory that's been allocated to that page pointer. yes she needs to know how much room she's got to work with, respect the boundaries bestie 💅

⭐ DESCRIPTION ⭐

so this is the handler for the config page read for SAS IO Unit page0 — the little worker bee that goes and fetches page0 for you 🐝

and here's the lowkey important bit: this routine checks ioc_status to decide whether the page read actually succeeded or flopped. like, it's doing a vibe check on the IOC's status field before it'll let you call it a win. if the status says good, we celebrate ✨; if not, well… 😭

🌈 RETURN 🌈

0 on success, non-zero on failure. iconic binary behaviour, ate and left no crumbs 💀

💜 SEE ALSO 💜

Kernel file ./drivers/scsi/mpi3mr/mpi3mr_fw.c — and like, the whole extended friend group:

okay that's the whole page, you're so welcome 💖 this little legend lives over in ./drivers/scsi/mpi3mr (that's the source, mwah), stamped October 2026 for the version-and-date of it all, and it answers to the name mpi3mr_cfg_get_sas_io_unit_pg0(9). go read your page0, bestie — periodt 🎀✨

📦 where this page comes from