mpi3mr_expander_phy_control(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 mpi3mr_expander_phy_control β€” expander phy control 🌸

okay so bestie, welcome to the kernel API manual page for mpi3mr_expander_phy_control, straight out of the mpi3mr crew πŸ’… this one's a lil function that pokes at an expander's phy, and honestly? iconic behavior. let's get into it 🫢


✨ SYNOPSIS ✨

int mpi3mr_expander_phy_control (struct mpi3mr_ioc *mrioc , struct
       sas_phy *phy , u8 phy_operation );

yep, that's the whole signature, no cap β€” three args in, an int out πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • mrioc β€” the adapter instance reference, like your main character's ID badge πŸ’³
  • phy β€” the SAS transport layer phy object, the actual phy baddie we're doing stuff to πŸ¦‹
  • phy_operation β€” the phy operation to be executed, i.e. what exactly we're asking that phy to do, ngl this is the important one πŸ‘‘

πŸ’– DESCRIPTION πŸ’–

so here's the vibe: this function issues an SMP passthru phy control request to execute a specific phy operation for a given expander device ✨ that's it, that's the whole thing β€” it's basically the messenger that walks your phy operation request over to the expander so it can actually happen. lowkey essential, highkey underappreciated 🌈


⭐ RETURN ⭐

  • 0 for success πŸŽ‰
  • non-zero for failure 😭 (yes, that's all it says β€” go forth and check your return values, bestie)

πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group, fr fr β€” go say hi to all of these 🫢


and that's the page, periodt πŸ’œ this lil slice of kernel lore lives in ./drivers/scsi/mpi3mr, dated October 2026 β€” mwah, go read the source, ily, bye πŸŽ€βœ¨

πŸ“¦ where this page comes from