mpt3sas_con...t_iounit_pg1(9)
π NAME π
okay so bestie, welcome to the Kernel API Manual β and before you ask, yes the header line up top is literally called mpt3sas_con...t_iounit_pg1(9) because somebody's terminal ran out of room. the real one, the whole entire name, is mpt3sas_config_get_iounit_pg1 β and what it does is obtain iounit page 1. that's it. that's the gig. π
β¨ SYNOPSIS β¨
int mpt3sas_config_get_iounit_pg1 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , Mpi2IOUnitPage1_t *config_page );
like, she takes three things and hands you back an int. no cap. π«Ά
π¦ ARGUMENTS π¦
iocβ the per adapter object, aka the main character of this whole driver situation πmpi_replyβ the reply mf payload returned from firmware, so like, the firmware's text back to you πconfig_pageβ the contents of the config page. yep. the page. the config one. π
πΈ CONTEXT πΈ
sleep.
that's the whole section. she sleeps. ngl it's giving "napping between classes" energy and honestly? iconic. π΄
β RETURN β
0 for success, non-zero for failure. lowkey the simplest vibe check in the whole kernel. if you get 0 you ate. if you get non-zero... well. π
π₯ SEE ALSO π₯
okay this list is long long, so grab a snack, but every single one of these is fr a real reference and we are not skipping a single one:
- Kernel file
./drivers/scsi/mpt3sas/mpt3sas_config.cstructconfig_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_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_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)
like I said. long long. but we read the whole thing because we're not cowards π
mwah, that's the page π§ this little beauty lives in ./drivers/scsi/mpt3sas, stamped October 2026, and she's out here doing the absolute most in the Kernel API Manual. go get that 0 return bestie, u got this πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms