sci_control...art_next_phy(9)

📦 version 7.3.1, in nixpkgs unstable

💅 sci_controller_start_next_phy — Kernel API Manual, bestie edition ✨

okay so this is the sci_controller_start_next_phy(9) page from the Kernel API Manual, and it's honestly so short it's giving "one-line text from your crush" energy, but we're gonna unpack it together 🫶

🌸 NAME 🌸

sci_controller_start_next_phy — start phy. that's it. that's the whole name. iconic brevity, no notes 💅

✨ SYNOPSIS ✨

enum sci_status sci_controller_start_next_phy (struct isci_host *ihost
);

so it hands you back an enum sci_status (the vibe check result, basically) and it takes exactly one thing. lowkey minimalist. we love a function that knows what it wants 🔥

🎀 ARGUMENTS 🎀

  • ihost — controller. yes bestie, that's the entire description. one whole word. the controller. give it a controller and let it cook 🍓

💖 DESCRIPTION 💖

okay so here's the tea: if all the phys have been started, then it attempts to transition the controller to the READY state and informs the user — that informing happens via sci_cb_controller_start_complete ✨

and like… that's the whole description. no cap. if all the phys aren't started? the manpage doesn't say. i'm not gonna make something up, that's not the move 🙈 we report exactly what's on the page and nothing more.

💀 friendly reminder that this function attempts the transition to READY — the page says "attempt," so don't go assuming it's guaranteed. we stay honest around here 🫶

🦋 SEE ALSO 🦋

all the siblings in the kernel file ./drivers/scsi/isci/host.c — go read these too, they're literally family:

🌈 okay that's the page!! it lives in ./drivers/scsi/isci, it's dated October 2026, and the header up top that got squished into sci_control...art_next_phy(9) is just this same page name being a little dramatic with the truncation 💀 anyway go start some phys, ily, bye 👑💜

📦 where this page comes from