mpt3sas_conf...e_iounit_pg1(9)
β¨ mpt3sas_config_get_pcie_iounit_pg1(9) β¨
okay so bestie, welcome to the Kernel API Manual π this one's a lil function page from the mpt3sas family β yes, the same mpt3sas that lives in ./drivers/scsi/mpt3sas. Buckle up, it's short and sweet, my fave kind.
πΈ NAME πΈ
mpt3sas_config_get_pcie_iounit_pg1 β literally just: obtain pcie iounit page 1. that's it. that's the whole vibe. π
π¦ SYNOPSIS π¦
int mpt3sas_config_get_pcie_iounit_pg1 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , Mpi26PCIeIOUnitPage1_t *config_page , u16
sz );
she returns an int, she takes four args, she's doing the absolute most with that signature ngl π
π ARGUMENTS π
iocβ the per adapter object π«Ά this is your adapter's whole personality, basically.mpi_replyβ reply mf payload returned from firmware β¨ the firmware's little answer-back moment.config_pageβ contents of the config page πΈ this is where the good stuff lands.szβ size of buffer passed inconfig_pageπ so she knows exactly how much room she's got, no cap.
β CONTEXT β
sleep. π΄
that's it, that's the context. she sleeps. respect her rest era fr fr.
π₯ DESCRIPTION π₯
Returns 0 for success, non-zero for failure. iconic behavior honestly β zero means slay, anything else means we're not okay π
π§ SEE ALSO π§
all the friends in the group chat π first the home file:
- Kernel file
./drivers/scsi/mpt3sas/mpt3sas_config.c
and the whole extended fam, in order, exactly as they appear:
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_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β¦ fifty entries?? she's thriving in the config ecosystem, truly the main character of mpt3sas_config.c π
k bye bestie, go read your config page π
this page is brought to you by the good people at ./drivers/scsi/mpt3sas, dated October 2026. mwah. π
π¦ 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