__mpi3mr_get...ddr_and_rphy(9)

💅 __mpi3mr_get...ddr_and_rphy(9) — Kernel API Manual, bestie edition 💅

okay so like… you found yourself in the kernel API manual, specifically the __mpi3mr_get...ddr_and_rphy(9) page, and honestly? iconic of you. this is the deep-lore corner of the docs and i'm here to make it make sense. no cap. 🫶

---

✨ NAME ✨

__mpi3mr_get_tgtdev_by_addr_and_rphy — target device search. that's it, that's the whole vibe. it's a lookup girlie. she finds things. 🔍

---

🌸 SYNOPSIS 🌸

struct mpi3mr_tgt_dev * __mpi3mr_get_tgtdev_by_addr_and_rphy (struct
mpi3mr_ioc *mrioc , u64 sas_address , struct sas_rphy *rphy );

three things go in, one pointer comes out. very demure, very mindful. 🎀

---

💖 ARGUMENTS 💖

• mrioc — the adapter instance reference. like, which controller are we even talking about, bestie? this one. 🦋
• sas_address — the SAS address of the device. it's a u64, it's the device's little name tag at the party. ⭐
• rphy — the SAS transport layer rphy object. yes, that rphy. the transport-layer one. 👑

---

🔥 DESCRIPTION 🔥

so what does she do? she searches for the target device using the SAS address and the rphy pointer together — both of them, not just one, we're thorough here 💅 — and then she returns the mpi3mr_tgt_dev object. like a bestie who knows exactly which group chat you mean. the way that lookup just works. periodt. ✨

---

🌈 RETURN 🌈

either a valid tget_dev or NULL. that's the whole range. she either found your device or she didn't, and she's not gonna sugarcoat it. 😭

ngl, if you get NULL back, that's your answer: nothing matched. no extra credit, no consolation prize. 💀

---

🧚 SEE ALSO 🧚

the kernel file in question lives at ./drivers/scsi/mpi3mr/mpi3mr_transport.c 🍓 and here's the whole extended friend group, all of them, no one left out:

• 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_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_host_add(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)

---

and that's the page, bestie 💜 mwah 💋

this lil artifact comes from ./drivers/scsi/mpi3mr, dated October 2026, and it's filed under the manual name __mpi3mr_get...ddr_and_rphy(9) — go off, you gorgeous lil kernel doc. 🎀✨🦋