mpi3mr_sas_host_add(9)

💅 mpi3mr_sas_host_add(9) — like, the whole vibe

okay so bestie, welcome to mpi3mr_sas_host_add(9) from the Kernel API Manual 🌸 — yes that's the manual name, we're folding it in early because we're polite like that. this is a little function but she's important, so let's get into it 🫶

---

✨ NAME ✨

mpi3mr_sas_host_add — create sas host object 💫

literally what it says on the tin: she makes the SAS host object happen. iconic behavior.

---

🦋 SYNOPSIS 🦋

void mpi3mr_sas_host_add (struct mpi3mr_ioc *mrioc );

not me copying this exactly character for character because i would NEVER mess up a signature 💅

---

🎀 ARGUMENTS 🎀

• mrioc — the adapter instance reference, aka your ticket to the whole controller. hand her the adapter and she'll do her thing 🌈

---

👑 DESCRIPTION 👑

so here's the tea ☕ — this function creates the controller's phy information and updates the SAS transport layer with that updated information.

and when does she do this? she's executed for the first device addition or a device info change event. so like, first-time meeting the device OR the device decided to switch up its info. both slay, both need this function 🧚

no cap, that's the whole description — she's short and she knows it.

---

⭐ RETURN ⭐

None. 💀

nothing. nada. she returns nothing and honestly? that's main character energy. don't go looking for a return value, there isn't one 🙈

---

🔥 SEE ALSO 🔥

okay this part is long and we are NOT skipping any of them, i don't care how many there are 💖 first up, the kernel file she lives in:

• Kernel file ./drivers/scsi/mpi3mr/mpi3mr_transport.c

and now, the full squad, every single one, no cuts, periodt ✨

• mpi3mr_post_transport_req(9)
• mpi3mr_report_manufacture(9)
• __mpi3mr_expander_find_by_handle(9)
• mpi3mr_is_expander_device(9)
• mpi3mr_get_sas_address(9)
• __mpi3mr_get_tgtdev_by_addr(9)
• mpi3mr_get_tgtdev_by_addr(9)
• mpi3mr_remove_device_by_sas_address(9)
• __mpi3mr_get_tgtdev_by_addr_and_rphy(9)
• mpi3mr_expander_find_by_sas_address(9)
• __mpi3mr_sas_node_find_by_sas_address(9)
• mpi3mr_parent_present(9)
• mpi3mr_convert_phy_link_rate(9)
• mpi3mr_delete_sas_phy(9)
• mpi3mr_add_sas_phy(9)
• mpi3mr_add_phy_to_an_existing_port(9)
• mpi3mr_delete_sas_port(9)
• mpi3mr_del_phy_from_an_existing_port(9)
• mpi3mr_sas_port_sanity_check(9)
• mpi3mr_set_identify(9)
• mpi3mr_add_host_phy(9)
• mpi3mr_add_expander_phy(9)
• mpi3mr_alloc_hba_port(9)
• mpi3mr_get_hba_port_by_id(9)
• mpi3mr_update_links(9)
• mpi3mr_sas_host_refresh(9)
• mpi3mr_sas_port_add(9)
• mpi3mr_sas_port_remove(9)
• struct host_port(9)
• mpi3mr_update_mr_sas_port(9)
• mpi3mr_refresh_sas_ports(9)
• mpi3mr_refresh_expanders(9)
• mpi3mr_expander_node_add(9)
• mpi3mr_expander_add(9)
• mpi3mr_expander_node_remove(9)
• mpi3mr_expander_remove(9)
• mpi3mr_get_sas_negotiated_logical_linkrate(9)
• mpi3mr_report_tgtdev_to_sas_transport(9)
• mpi3mr_remove_tgtdev_from_sas_transport(9)
• mpi3mr_get_port_id_by_sas_phy(9)
• mpi3mr_get_port_id_by_rphy(9)
• mpi3mr_get_expander_phy_error_log(9)
• mpi3mr_transport_get_linkerrors(9)
• mpi3mr_transport_get_enclosure_identifier(9)
• mpi3mr_transport_get_bay_identifier(9)
• mpi3mr_expander_phy_control(9)
• mpi3mr_transport_phy_reset(9)
• mpi3mr_transport_phy_enable(9)
• mpi3mr_transport_phy_speed(9)
• mpi3mr_map_smp_buffer(9)
• mpi3mr_unmap_smp_buffer(9)
• mpi3mr_transport_smp_handler(9)

like i said. the whole squad. ate and left no crumbs 🍓

---

and that's the page, bestie 🎀 cute little sign-off: this one comes from the source tree at ./drivers/scsi/mpi3mr, dated October 2026, and the page itself is mpi3mr_sas_host_add(9) because obviously 💜 go forth and add your SAS host ✨