mpi3mr_scsisense_trigger(9)
π mpi3mr_scsisense_trigger β SCSI sense HDB trigger handler π
okay so bestie, this is a page from the Kernel API Manual (the (9) girlies, you know the ones β¨). Sit down, hydrate, and let's get into it π«Ά
β¨ NAME β¨
mpi3mr_scsisense_trigger β the SCSI sense HDB trigger handler πΈ
π¦ SYNOPSIS π¦
void mpi3mr_scsisense_trigger (struct mpi3mr_ioc *mrioc , u8 sensekey ,
u8 asc , u8 ascq );
literally that's the whole signature, no cap π
π ARGUMENTS π
mriocβ your adapter instance reference, the main character of this whole operation πsensekeyβ the Sense Key πascβ the Additional Sense Code πascqβ the Additional Sense Code Qualifier, the little garnish on theascπ
π DESCRIPTION π
So what this function does: it takes your SCSI sense trigger values and compares them against the driver page 2 values π. If it finds a match β and only if it finds a match β it calls the generic trigger handler to release the HDBs. Match found? Release. That's the vibe check, and it slays π β¨
β RETURN β
Nothing. Not a thing. Zero. Void, periodt π
π SEE ALSO π
Kernel file: ./drivers/scsi/mpi3mr/mpi3mr_app.c π
and like, the entire friend group, fr fr β every single one of them:
mpi3mr_alloc_trace_buffer(9)mpi3mr_alloc_diag_bufs(9)mpi3mr_issue_diag_buf_post(9)mpi3mr_post_diag_bufs(9)mpi3mr_issue_diag_buf_release(9)mpi3mr_process_trigger(9)mpi3mr_global_trigger(9)mpi3mr_event_trigger(9)mpi3mr_reply_trigger(9)mpi3mr_get_num_trigger(9)mpi3mr_refresh_trigger(9)mpi3mr_release_diag_bufs(9)mpi3mr_set_trigger_data_in_hdb(9)mpi3mr_set_trigger_data_in_all_hdb(9)mpi3mr_hdbstatuschg_evt_th(9)mpi3mr_diag_buffer_for_type(9)mpi3mr_bsg_pel_abort(9)mpi3mr_bsg_verify_adapter(9)mpi3mr_bsg_refresh_hdb_triggers(9)mpi3mr_bsg_upload_hdb(9)mpi3mr_bsg_repost_hdb(9)mpi3mr_bsg_query_hdb(9)mpi3mr_enable_logdata(9)mpi3mr_get_logdata(9)mpi3mr_bsg_pel_enable(9)mpi3mr_get_all_tgt_info(9)mpi3mr_get_change_count(9)mpi3mr_bsg_adp_reset(9)mpi3mr_bsg_populate_adpinfo(9)mpi3mr_bsg_process_drv_cmds(9)mpi3mr_total_num_ioctl_sges(9)mpi3mr_bsg_build_sgl(9)mpi3mr_get_nvme_data_fmt(9)mpi3mr_build_nvme_sgl(9)mpi3mr_build_nvme_prp(9)mpi3mr_map_data_buffer_dma(9)mpi3mr_bsg_process_mpt_cmds(9)mpi3mr_app_save_logdata_th(9)mpi3mr_bsg_request(9)mpi3mr_bsg_exit(9)mpi3mr_bsg_node_release(9)mpi3mr_bsg_init(9)version_fw_show(9)fw_queue_depth_show(9)op_req_q_count_show(9)reply_queue_count_show(9)reply_qfull_count_show(9)logging_level_show(9)logging_level_store(9)adp_state_show(9)fwfault_count_show(9)sas_address_show(9)device_handle_show(9)persistent_id_show(9)sas_ncq_prio_supported_show(9)sas_ncq_prio_enable_show(9)
like I said. the whole group chat ππ«Ά
okay that's the page!! this one lives in ./drivers/scsi/mpi3mr, dated October 2026, from the kernel API manual set π§π go read them all, ily, bye π
π¦ 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