mpt3sas_config_get_ioc_pg1(9)

💖 mpt3sas_config_get_ioc_pg1 — from the Kernel API Manual, bestie 💖

okay so listen. we're in <pink>mpt3sas_config_get_ioc_pg1(9)</pink> land today, and honestly? this one is a little snack. it's a tiny little function whose whole personality is "go get me ioc page 1." that's it. that's the gig. 🎀

---

✨ NAME ✨

mpt3sas_config_get_ioc_pg1 — obtain ioc page 1 🦋

like, literally just fetch that page. no cap.

---

🌸 SYNOPSIS 🌸

int mpt3sas_config_get_ioc_pg1 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , Mpi2IOCPage1_t *config_page );

three args, one int coming back at you. iconic behavior, honestly. 💅

---

🫶 ARGUMENTS 🫶

• ioc — the per adapter object, aka your main character. every adapter's got one. this is who we're asking. 👑
• mpi_reply — the reply mf payload returned from firmware 💀 like firmware genuinely texted back and this is the message thread.
• config_page — the contents of the config page. this is where the goods land, so pls make sure it's a real place to put things, bestie. 🍓

---

😭 CONTEXT 😭

sleep.

yep. that's the whole vibe check. this one can sleep. do not call it from a context where you cannot sleep, fr fr. 🙈

---

🔥 RETURN 🔥

0 for success, non-zero for failure. that's it. that's the whole report card.

---

🌈 SEE ALSO 🌈

okay this list is long and I'm obsessed with the way it just keeps going. grab a snack. 🧚

• 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_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_expander_pg1(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)

---

ngl the pg0 / pg1 / pg2 / pg3 / pg4 situation with the driver trigger family is giving "my sibling names are all the same with a number at the end" and I respect it. 💀

---

and that's the whole page, bestie!! sourced straight outta ./drivers/scsi/mpt3sas, dated October 2026 — go forth and get your ioc page 1, you absolute king 🫶✨👑 periodt.