mpt3sas_config_get_phy_pg0(9)
π mpt3sas_config_get_phy_pg0 β obtain phy page 0
okay so bestie, welcome to the Kernel API Manual entry for mpt3sas_config_get_phy_pg0(9) β literally the lil' function that goes and obtains phy page 0 for you. no cap, that's the whole vibe. β¨
πΈ SYNOPSIS πΈ
int mpt3sas_config_get_phy_pg0 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , Mpi2SasPhyPage0_t *config_page , u32
phy_number );
she returns an int, she takes four args, she's iconic. periodt. π
π ARGUMENTS π
iocβ the per adapter object π«Ά like, your whole adapter's main character.mpi_replyβ the reply mf payload returned from firmware. yes "mf" is in the original, iykyk ππ₯config_pageβ contents of the config page. she's the container, she holds the goods πphy_numberβ phy number. that's it. that's the whole description bestie, no notes π
π¦ CONTEXT π¦
sleep. π΄
like literally, that's the context. she sleeps. she's lowkey a sleepy girl and that's valid. ngl you should not be calling this from somewhere that can't sleep β that's giving chaos energy π
β RETURN β
0 for success, non-zero for failure. simple as. zero = slay π, anything else = we do not stan π
π SEE ALSO π
Kernel file ./drivers/scsi/mpt3sas/mpt3sas_config.c and the whole friend group β go give them a follow, they're all linked together fr fr:
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_expander_pg1(9)mpt3sas_config_get_enclosure_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)
and that's the whole page bestie!! π§ no gatekeeping, every single reference kept, every detail intact β we ate and left no crumbs. π
source: ./drivers/scsi/mpt3sas Β· date: October 2026 β¨ mwah, love u, go read ur kernel docs π«Ά
π¦ 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