sci_phy_comp...ink_training(9)

🌸 NAME 🌸

sci_phy_complete_link_training — bestie, this is the function that does all the processing that's common to every protocol once link training is done. Like, the shared afterparty cleanup. 💅

✨ SYNOPSIS ✨

void sci_phy_complete_link_training (struct isci_phy *iphy , enum
sas_linkrate max_link_rate , u32 next_state );

No cap, that's the whole signature. Returns void, so don't go looking for a return value, she gives you nothing back and that's iconic of her. 🎀

🦋 ARGUMENTS 🦋

• iphy — this one's the phy object for which link training has completed. The main character of this whole situation, honestly. ✨
• max_link_rate — the maximum link rate that gets associated with this phy. It's an enum sas_linkrate, so it's giving "please pick from the list." 🔥
• next_state — a u32 that specifies the next state for the phy's starting sub-state machine. Yes, "starting sub-state machine" is the real name, and yes, it lowkey sounds like a vibe check for a tiny robot. 🧚 It's literally where the phy goes next.

👑 SEE ALSO 👑

Okay so the kernel file living at ./drivers/scsi/isci/phy.c is the homegirl here, and she's bringing her whole friend group:

• phy_get_non_dummy_port(9)
• sci_phy_setup_transport(9)
• scu_link_layer_stop_protocol_engine(9)
• scu_link_layer_tx_hard_reset(9)
• isci_phy_control(9)

Read those if you want the full lore, iykyk. 📚💜

Fr fr, this one's a kernel API manual page, so like... respect the kernel, bestie. 🫶

🌈 That's the whole page! The source is ./drivers/scsi/isci and it's dated October 2026, and the page is sci_phy_comp...ink_training(9) — slay, go forth and complete that link training. 💖⭐