mpt3sas_conf..._trigger_pg1(9)
π mpt3sas_conf..._trigger_pg1(9) β Kernel API Manual, but make it make sense
okay so bestie, welcome to the Kernel API Manual entry for mpt3sas_conf..._trigger_pg1(9) β yes the name is long, yes it's giving "my wifi password is a paragraph", but we're gonna get through it together π«Ά
β¨ NAME β¨
mpt3sas_config_update_driver_trigger_pg1 β update driver trigger page 1. that's the whole gig. iconic, honestly π
πΈ SYNOPSIS πΈ
int mpt3sas_config_update_driver_trigger_pg1 (struct MPT3SAS_ADAPTER
*ioc , struct SL_WH_MASTER_TRIGGER_T *master_tg , bool set );
literally just three args and an int coming back at you. no cap β¨
π¦ ARGUMENTS π¦
iocβ the per adapter object π this is your adapter's whole little world.master_tgβ the Master trigger bit map. that's the map, bestie, respect it.setβ set ot clear trigger values π (yes it says "ot", we're keeping it, typos are also main characters)
π€ CONTEXT π€
sleep.
not me, the function. it's a sleep.-context function. so like. don't call it from somewhere spicy π₯
β DESCRIPTION β
it returns 0 for success, and non-zero for failure. that's it, that's the vibe check π
0 = slay, anything else = something went sideways.
π SEE ALSO π
the whole friend group, fr fr β go read these too:
Kernel file ./drivers/scsi/mpt3sas/mpt3sas_config.cstruct 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_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_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)
that's 58 entries and we listed every single one because we do not do half-finished homework in this house π§
and that's the page!! sourced from ./drivers/scsi/mpt3sas, dated October 2026, filed under mpt3sas_conf..._trigger_pg1(9). go forth and update that trigger page 1, bestie β you 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