phy_get_non_dummy_port(9)

🌸 phy_get_non_dummy_port 🌸

okay so bestie, welcome to the Kernel API Manual entry for phy_get_non_dummy_port and honestly? it's a little baddie of a function. let's get into it 💖

---

✨ NAME ✨

phy_get_non_dummy_port — this method returns the port that's currently containing this phy. and like… if the phy is currently contained by the dummy port, then the phy is considered to not be part of a port. that's the whole vibe check. no cap. 💅

---

🦋 SYNOPSIS 🦋

struct isci_port * phy_get_non_dummy_port (struct isci_phy *iphy );

that's it. that's the signature. icon behaviour honestly.

---

🎀 ARGUMENTS 🎀

• iphy — this parameter specifies the phy for which you wanna retrieve the containing port. like, "which phy, bestie?" and you tell it. 🫶

---

🧚 DESCRIPTION 🧚

okay so here's the tea ☕ — this method returns a handle to a port that contains the supplied phy. simple enough, right? but wait, there's a little drama:

• NULL — this value is returned if the phy is not part of a real port (i.e. it's contained in the dummy port). so if you get NULL back, that phy is lowkey just hanging out in the dummy port, not a real one. 🙈
• !NULL — all other values indicate a handle/pointer to the port containing the phy. so like, anything that isn't NULL means you got a real one, and it slayed. 🔥

ngl, the whole "dummy port" thing is the main character here — if your phy is in there, it doesn't count as being part of a port. periodt. 👑

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/scsi/isci/phy.c
• sci_phy_setup_transport(9)
• sci_phy_complete_link_training(9)
• scu_link_layer_stop_protocol_engine(9)
• scu_link_layer_tx_hard_reset(9)
• isci_phy_control(9)

go read those too, they're all part of the same friend group fr fr 🫶✨

---

and that's the whole page, bestie!! brought to you by the source ./drivers/scsi/isci, dated October 2026 — mwah, ily, go call phy_get_non_dummy_port responsibly 💜🎀🌷