mpt3sas_con...expander_pg0(9)
π mpt3sas_config_get_expander_pg0 β obtain expander page 0
okay so bestie, welcome to the Kernel API Manual β¨ β section 9 of the Kernel API Manual, to be exact β and today's main character is mpt3sas_con...expander_pg0(9), aka mpt3sas_config_get_expander_pg0. yes the name is long. yes it ate. π
πΈ NAME πΈ
mpt3sas_config_get_expander_pg0 β obtain expander page 0
like, it goes and gets you an expander page 0. that's the whole vibe. no cap. π¦
β¨ SYNOPSIS β¨
int mpt3sas_config_get_expander_pg0 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , Mpi2ExpanderPage0_t *config_page , u32
form , u32 handle );
it's giving "five arguments, all of them matter", and honestly? iconic. π
π ARGUMENTS π
iocβ per adapter object. the whole adapter's like, personality file, yk? π₯mpi_replyβ reply mf payload returned from firmware. the firmware claps back and this is where it lands πconfig_pageβ contents of the config page. the actual tea. the goods. πformβGET_NEXT_HANDLEorHANDLE. pick your fighter, literally, you have to pick one. πhandleβ expander handle. it's the expander's little name tag π·οΈ
π§ CONTEXT π§
sleep.
yes that's it. that's the whole note. it sleeps. put it to bed, let it nap, don't you dare call it from somewhere spicy π like, respect the nap.
π RETURN π
0 for success, non-zero for failure. that's the binary of it all β either she slayed or she didn't π«Ά
π¦ SEE ALSO π¦
lowkey the whole friend group showed up, and there's a lot of them. all under 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_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. the whole group chat. π
ngl if you're looking for the source of truth, she lives in ./drivers/scsi/mpt3sas β that's the directory, periodt. π
and that's the page, bestie β ./drivers/scsi/mpt3sas, October 2026, Kernel API Manual, section 9. go get that expander page 0 and slay π
β¨
π¦ 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