sci_port_gen...k_up_handler(9)

💖 NAME 💖

okay bestie, welcome to the Kernel API Manual — this is the sci_port_gen...k_up_handler(9) page. The function is sci_port_general_link_up_handler, and the whole vibe is: phy can be assigned to port? ✨

🎀 SYNOPSIS 🎀

void sci_port_general_link_up_handler (struct isci_port *iport , struct isci_phy *iphy , u8 flags );

🌸 ARGUMENTS 🌸

• iport — the sci_port object for a port that has a phy which has gone link up. 💅
• iphy — this is the struct isci_phy object that has gone link up. 🦋
• flags — PF_RESUME, PF_NOTIFY to sci_port_activate_phy. 🎀

✨ DESCRIPTION ✨

So this function determines if this phy can be assigned to this port. If the phy is not a valid PHY for this port, then the function will notify the user. 🔔

And bestie, here’s the rule: a PHY can only be part of a port if its attached SAS ADDRESS is the same as all other PHYs in the same port. periodt. 💅

🦋 SEE ALSO 🦋

Kernel file: ./drivers/scsi/isci/port.c

• sci_port_get_properties(9)
• isci_port_link_down(9)
• isci_port_hard_reset_complete(9)
• sci_port_is_phy_mask_valid(9)
• sci_port_construct_dummy_rnc(9)
• sci_port_is_wide(9)
• sci_port_link_detected(9)
• sci_port_post_dummy_request(9)
• sci_port_abort_dummy_request(9)
• sci_port_resume_port_task_scheduler(9)
• sci_port_ready_substate_operational_exit(9)
• sci_port_add_phy(9)
• sci_port_remove_phy(9)

💅 that’s the whole page, bestie — brought to you by ./drivers/scsi/isci, dated October 2026, and it’s the sci_port_gen...k_up_handler(9) entry. no cap, that’s a wrap 🫶