mpt3sas_conf..._trigger_pg4(9)
π
mpt3sas_conf..._trigger_pg4(9) β Kernel API Manual, bestie edition β¨
Okay so picture this: you're deep in the Kernel API Manual, poking at the mpt3sas driver, and you need to touch driver trigger page 4. That's it, that's the whole vibe of this page. Buckle up π
β¨ NAME β¨
mpt3sas_config_update_driver_trigger_pg4 β literally just updates the driver trigger page 4. Iconic, lowkey self-explanatory, and honestly? We love a function that tells you exactly what it does. π
πΈ SYNOPSIS πΈ
int mpt3sas_config_update_driver_trigger_pg4 (struct MPT3SAS_ADAPTER
*ioc , struct SL_WH_MPI_TRIGGERS_T *mpi_tg , bool set );
It returns an int, it takes a per-adapter object, a trigger list, and a bool. Three arguments, zero drama. π¦
π«Ά ARGUMENTS π«Ά
iocβ the per adapter object π like, your whole adapter's main character.mpi_tgβ the mpi trigger list π this is the trigger list you're working with.setβ set or clear trigger values β flip this and you're either setting or clearing, no in-between.
π CONTEXT π
sleep.
fr fr, it sleeps. This one's not playing around β bestie is allowed to block. Do not call it from atomic context unless you enjoy chaos π
π₯ DESCRIPTION π₯
Returns 0 for success, non-zero for failure. That's the whole bit, no cap β clean little return-code contract, exactly the way we like it. β
π SEE ALSO π
This is the part where the page just π«Ά goes off β the whole friend group is here. Kernel file ./drivers/scsi/mpt3sas/mpt3sas_config.c and friends:
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_update_driver_trigger_pg3(9)mpt3sas_config_get_driver_trigger_pg4(9)_config_set_driver_trigger_pg4(9)mpt3sas_config_get_volume_handle(9)mpt3sas_config_get_volume_wwid(9)
Like, every pg0 through pg4 trigger sibling is accounted for β not me checking the list twice πβ¨
And that's the page, bestie!! π§
This one lives in the kernel source at ./drivers/scsi/mpt3sas, dated October 2026 β so go forth, update that page 4, 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