mpt3sas_conf..._trigger_pg3(9)
π mpt3sas_conf..._trigger_pg3(9) π
okay so bestie, we're deep in the Kernel API Manual today β yes, the actual kernel, not your laptop's vibes β and this one is a little legend from the mpt3sas corner of the world π
β¨ NAME β¨
mpt3sas_config_update_driver_trigger_pg3 β update driver trigger page 3. that's the whole job, she's a page-three updater and she's iconic for it π
πΈ SYNOPSIS πΈ
int mpt3sas_config_update_driver_trigger_pg3 (struct MPT3SAS_ADAPTER
*ioc , struct SL_WH_SCSI_TRIGGERS_T *scsi_tg , bool set );
literally just three args, no drama, we love a signature that fits on the screen π«Ά
π¦ ARGUMENTS π¦
iocβ per adapter object. like, the adapter in question, her personal file ποΈscsi_tgβ scsi trigger list. the actual list of triggers we're messing with π₯setβ set ot clear trigger values. (yes the manpage says "ot", it's giving typo but we're keeping it fr fr β it means set or clear, pick a lane babes) π
π CONTEXT π
sleep.
that's it. that's the context. she naps π΄ β so don't be calling her from anywhere that can't sleep, iykyk.
β DESCRIPTION β
Returns 0 for success, non-zero for failure. that's the entire deal β you call her, she updates driver trigger page 3, and she tells you how it went. no cap, no hidden lore π
π SEE ALSO π
the whole friend group, all linked up π she doesn't roll alone:
- the 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_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_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, she knows everyone at the config party π
lowkey a serve that a single function has this many siblings. family reunion when? π
and that's the whole page bestie β sourced from ./drivers/scsi/mpt3sas, dated October 2026, still serving kernel-api realness. 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