sci_port_con...nt_find_port(9)

💖 NAME 💖

sci_port_configuration_agent_find_port —

yes bestie, that's the whole NAME entry — the dash is literally just sitting there, no extra subtitle, periodt. 🫶

🎀 SYNOPSIS 🎀

struct isci_port * sci_port_configuration_agent_find_port (struct
       isci_host *ihost , struct isci_phy *iphy );

🌸 ARGUMENTS 🌸

• ihost — the controller object used for the port search. 👑
• iphy — the phy object to match. 🦋

✨ DESCRIPTION ✨

okay so this routine will find a matching port for the phy 💅. “Matching” here means the port and the phy both have the same broadcast sas address and the same received sas address — both same-same, not one or the other, iykyk.

The return vibe is the port address if the port can be found to match the phy, or NULL if there is no matching port for the phy. The original wording also gives us “The port address or the NULL if there is no matching port” and “port address if the port can be found to match the phy. NULL if there is no matching port for the phy.” So: matching port found = port address; no matching port = NULL. no cap. 😭

🔥 SEE ALSO 🔥

• Kernel file ./drivers/scsi/isci/port_config.c 🍓
• sci_sas_address_compare(9),
• sci_port_configuration_agent_validate_ports(9),
• sci_mpc_agent_link_down(9), sci_apc_agent_link_up(9),
• sci_apc_agent_link_down(9)

mwah 💋 this lil page comes from the ./drivers/scsi/isci source, dated October 2026, and the footer label is sci_port_con...nt_find_port(9). bye bestie, go find that port ✨