scsi_is_sas_rphy(9)

🌸 NAME 🌸

Okay bestie, welcome to the scsi_is_sas_rphy(9) page from the Kernel API Manual — and it's lowkey here to answer one tiny iconic question: check if a struct device represents a SAS remote PHY. That's the whole assignment, no cap. 💅

✨ SYNOPSIS ✨

The signature is exactly this, bestie — yes, keep the spacing:

int scsi_is_sas_rphy (const struct device *dev );

It's giving “small function, big main character energy.” 🦋

🎀 ARGUMENTS 🎀

• dev — the device to check. That's the one and only argument, periodt. 💖

🔥 RETURN 🔥

1 if the device represents a SAS remote PHY, 0 else. Literally binary, bestie — no in-between, no maybes, no “it depends.” ✨

🦋 SEE ALSO 🦋

Okay so this page chills in the Kernel file ./drivers/scsi/scsi_transport_sas.c, and it rolls with a whole squad of linked besties. Obsessed with this friend group, honestly:

• 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_expander_alloc(9)
• sas_rphy_add(9)
• sas_rphy_free(9)
• sas_rphy_delete(9)
• sas_rphy_unlink(9)
• sas_rphy_remove(9)
• sas_attach_transport(9)
• sas_release_transport(9)

Mwah 💖 — source/version: ./drivers/scsi, date: October 2026. Bye bestie, go check those devices! 🫶✨