mpt3sas_con...expander_pg1(9)

💅 NAME

mpt3sas_config_get_expander_pg1 — bestie, this is the one that goes and obtains expander page 1 for you ✨ (this page is from the Kernel API Manual, and we're about to make it make sense, iykyk 🫶)

---

🌸 SYNOPSIS

int mpt3sas_config_get_expander_pg1 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , Mpi2ExpanderPage1_t *config_page , u32
phy_number , u16 handle );

That's the whole vibe right there — one function, five args, zero drama. 🎀

---

✨ ARGUMENTS (the cast, the main characters) 👑

• ioc — your per adapter object 💖 literally the adapter's whole personality lives in here.
• mpi_reply — the reply mf payload that gets returned from firmware 🔥 ("mf" = message frame, she's built different).
• config_page — the contents of the config page. this is where the good stuff ends up after the call 🦋
• phy_number — phy number. that's it, that's the arg 🙈 give it the phy you want.
• handle — expander handle 👑 your golden ticket to the specific expander you're asking about.

---

😴 CONTEXT

sleep. yes bestie that's the entire context. this one sleeps 😭 so don't call it somewhere that can't nap, no cap.

---

🫶 RETURN

0 for success, non-zero for failure. ✨ zero means slay, anything else means something went sideways — go check.

---

🌈 SEE ALSO

okay so the fam is huge, and here's every single one of them, in order, no cap, nobody left behind 💜:

• Kernel file ./drivers/scsi/mpt3sas/mpt3sas_config.c
• struct config_request(9), _config_display_some_debug(9), _config_alloc_config_dma_memory(9), _config_free_config_dma_memory(9)
• mpt3sas_config_done(9), _config_request(9)
• mpt3sas_config_get_manufacturing_pg0(9), mpt3sas_config_get_manufacturing_pg1(9), mpt3sas_config_get_manufacturing_pg10(9), mpt3sas_config_get_manufacturing_pg11(9), mpt3sas_config_set_manufacturing_pg11(9)
• mpt3sas_config_get_bios_pg2(9), mpt3sas_config_get_bios_pg3(9), mpt3sas_config_set_bios_pg4(9), mpt3sas_config_get_bios_pg4(9)
• mpt3sas_config_get_iounit_pg0(9), mpt3sas_config_get_iounit_pg1(9), mpt3sas_config_set_iounit_pg1(9), mpt3sas_config_get_iounit_pg3(9), mpt3sas_config_get_iounit_pg7(9), mpt3sas_config_get_iounit_pg8(9)
• mpt3sas_config_get_ioc_pg8(9), mpt3sas_config_get_ioc_pg1(9), mpt3sas_config_set_ioc_pg1(9)
• mpt3sas_config_get_sas_device_pg0(9), mpt3sas_config_get_pcie_device_pg0(9), mpt3sas_config_get_pcie_iounit_pg1(9), mpt3sas_config_get_pcie_device_pg2(9)
• mpt3sas_config_get_number_hba_phys(9), mpt3sas_config_get_sas_iounit_pg0(9), mpt3sas_config_get_sas_iounit_pg1(9), mpt3sas_config_set_sas_iounit_pg1(9)
• mpt3sas_config_get_expander_pg0(9), mpt3sas_config_get_enclosure_pg0(9)
• mpt3sas_config_get_phy_pg0(9), mpt3sas_config_get_phy_pg1(9)
• mpt3sas_config_get_raid_volume_pg1(9), mpt3sas_config_get_number_pds(9), mpt3sas_config_get_raid_volume_pg0(9), mpt3sas_config_get_phys_disk_pg0(9)
• mpt3sas_config_get_driver_trigger_pg0(9), _config_set_driver_trigger_pg0(9), mpt3sas_config_update_driver_trigger_pg0(9)
• mpt3sas_config_get_driver_trigger_pg1(9), _config_set_driver_trigger_pg1(9), mpt3sas_config_update_driver_trigger_pg1(9)
• mpt3sas_config_get_driver_trigger_pg2(9), _config_set_driver_trigger_pg2(9), mpt3sas_config_update_driver_trigger_pg2(9)
• mpt3sas_config_get_driver_trigger_pg3(9), _config_set_driver_trigger_pg3(9), mpt3sas_config_update_driver_trigger_pg3(9)
• mpt3sas_config_get_driver_trigger_pg4(9), _config_set_driver_trigger_pg4(9), mpt3sas_config_update_driver_trigger_pg4(9)
• mpt3sas_config_get_volume_handle(9), mpt3sas_config_get_volume_wwid(9)

---

fr fr that's all of them, go read the ones you actually need 💀

okay and one cute little sign-off: this page lives in ./drivers/scsi/mpt3sas, it's the October 2026 edition, and it goes out to mpt3sas_con...expander_pg1(9). ily, go get that page 1 💖✨🎀🦋