mptsas_scan_sas_topology(9)

✨ mptsas_scan_sas_topology ✨ (section 9 of the kernel API manual, bestie 💅)

okay so picture this: it's section 9, it's the kernel API manual, and the main character of this page is mptsas_scan_sas_topology — the function that goes out and scans the brand-new SAS topology for you. it's basically the "who's here??" moment that happens as part of a probe or a rescan 🦋

🌸 NAME 🌸

mptsas_scan_sas_topology — scans new SAS topology (part of probe or rescan) ✨

🎀 SYNOPSIS 🎀

void mptsas_scan_sas_topology (MPT_ADAPTER *ioc );

that's it. that's the whole call. void, no return value, just vibes and a pointer 🫶

💖 ARGUMENTS 💖

• ioc — a pointer to the MPT_ADAPTER structure, aka the whole adapter situation you're scanning. hand it over and let the function do its thing 👑

👑 SEE ALSO 👑

like. the whole extended friend group. every single one of these, no skips 🔥

• Kernel file ./drivers/message/fusion/mptsas.c
• mptsas_find_portinfo_by_sas_address(9)
• mptsas_add_device_component(9)
• mptsas_add_device_component_by_fw(9)
• mptsas_add_device_component_starget_ir(9)
• mptsas_add_device_component_starget(9)
• mptsas_del_device_component_by_os(9)
• mptsas_del_device_components(9)
• mptsas_find_vtarget(9)
• mptsas_target_reset(9)
• mptsas_target_reset_queue(9)
• mptsas_schedule_target_reset(9)
• mptsas_taskmgmt_complete(9)
• mptsas_ioc_reset(9)
• enum device_state(9)
• mptsas_add_end_device(9)
• mptsas_del_end_device(9)
• mptsas_firmware_event_work(9)
• mptsas_eh_timed_out(9)
• mptsas_exp_repmanufacture_info(9)
• mptsas_delete_expander_siblings(9)
• mptsas_expander_delete(9)
• mptsas_send_expander_event(9)
• mptsas_expander_add(9)
• mptsas_probe_expanders(9)
• mptsas_find_phyinfo_by_phys_disk_num(9)
• mptsas_issue_tm(9)
• mptsas_broadcast_primitive_work(9)

and that's the page, bestie 💜 this little icon lives over in <code>./drivers/message/fusion</code> and it's dated October 2026 — go scan some topology, slay, periodt 🌈✨