scsi_is_sas_port(9)

💅 scsi_is_sas_port(9) — like, the Kernel API Manual era 🎀

okay bestie, welcome to scsi_is_sas_port(9), a little function from the Kernel API Manual that's honestly giving "tiny but crucial" energy ✨

---

🌸 NAME 🌸

scsi_is_sas_port — the vibe check that tells you if a struct device is actually representing a SAS port 👑

---

🦋 SYNOPSIS 🦋

int scsi_is_sas_port (const struct device *dev );

bestie it takes exactly one thing and it returns an int, no cap, that's the whole mood 💅

---

🎀 ARGUMENTS 🎀

• dev — the device you're side-eyeing 🙈 literally just "device to check", that's it.

---

⭐ RETURN ⭐

• 1 if the device represents a SAS Port 🎉 slay, it's a port!
• 0 else 🫶 nope, not a port, moving on.

that's the entire return contract, and honestly? iconic. periodt. 💖

---

🌈 SEE ALSO 🌈

the whole friend group lives in the kernel file ./drivers/scsi/scsi_transport_sas.c — go say hi to the rest of the squad:

• sas_remove_children(9)
• sas_remove_host(9)
• sas_get_address(9)
• sas_tlr_supported(9)
• sas_disable_tlr(9)
• sas_enable_tlr(9)
• sas_ata_ncq_prio_supported(9)
• sas_phy_alloc(9)
• sas_phy_add(9)
• sas_phy_free(9)
• sas_phy_delete(9)
• scsi_is_sas_phy(9)
• sas_port_alloc(9)
• sas_port_alloc_num(9)
• sas_port_add(9)
• sas_port_free(9)
• sas_port_delete(9)
• sas_port_get_phy(9)
• sas_port_add_phy(9)
• sas_port_delete_phy(9)
• sas_rphy_initialize(9)
• sas_end_device_alloc(9)
• sas_expander_alloc(9)
• sas_rphy_add(9)
• sas_rphy_free(9)
• sas_rphy_delete(9)
• sas_rphy_unlink(9)
• sas_rphy_remove(9)
• scsi_is_sas_rphy(9)
• sas_attach_transport(9)
• sas_release_transport(9)

like, yes, that's a lot of sas_* names 😭 but every single one of them is a real one and they all belong on this list, so don't come for me 💀

---

and that's the whole page, bestie 🧚💜 this came from the ./drivers/scsi corner of the world, dated October 2026, and it's filed under the manual name scsi_is_sas_port(9) — mwah, bye! 🍓🔥