sas_expander_alloc(9)

💖 NAME 💖

sas_expander_alloc — allocate an rphy for an end device. Bestie, this is the sas_expander_alloc(9) page from the Kernel API Manual, and it’s giving “small function, big kernel energy” ✨

---

✨ SYNOPSIS ✨

Exact shape, no cap:

struct sas_rphy * sas_expander_alloc (struct sas_port *parent , enum
sas_device_type type );

---

🎀 ARGUMENTS 🎀

• parent — which port. That’s the one, bestie 🫶
• type — SAS_EDGE_EXPANDER_DEVICE or SAS_FANOUT_EXPANDER_DEVICE. Pick your fighter, but those are the two in the docs 👑

---

🦋 DESCRIPTION 🦋

Allocates an SAS remote PHY structure, connected to parent. It’s literally the allocation moment, so treat it with main character energy 💅

---

🌸 RETURN 🌸

SAS PHY allocated, or NULL if the allocation failed. Check for that NULL, bestie — allocation can fail and that is not the vibe 😭

---

🌈 SEE ALSO 🌈

Kernel file: ./drivers/scsi/scsi_transport_sas.c

The whole squad, in order:

• 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), scsi_is_sas_port(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_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)

---

okay that’s the whole page, bestie 🫶 This iconic little manpage is sourced from ./drivers/scsi, dated October 2026, and it’s literally sas_expander_alloc(9). periodt 💅✨