sci_controller_start_task(9)

💅 sci_controller_start_task(9) — like, the whole vibe

okay so bestie, welcome to the Kernel API Manual ✨ this one's about sci_controller_start_task(9) and honestly? she's a little connector-function diva whose whole job is kicking off task management requests. no cap.

🌸 NAME 🌸

sci_controller_start_task — this method is called by the SCIC user to send/start a framework task management request 💌 (yes, "SCIC user" — that's you, you're the user, own it)

🎀 SYNOPSIS 🎀

enum sci_status sci_controller_start_task (struct isci_host *ihost ,
struct isci_remote_device *idev , struct isci_request *ireq );

like, look at that signature. three pointers, one enum sci_status return. iconic behavior only 👑

🦋 ARGUMENTS 🦋

• ihost — the handle to the controller object for which to start the task management request. this is your controller babe, the main character 🌟
• idev — the handle to the remote device object for which to start the task management request. the remote device in question, lowkey essential 🫶
• ireq — the handle to the task request object to start. the actual request getting launched into the world, go off 🚀

👑 SEE ALSO 👑

like, the whole friend group 💖 — Kernel file ./drivers/scsi/isci/host.c, plus:

• isci_host_start_complete(9)
• sci_controller_get_suggested_start_timeout(9)
• sci_controller_start_next_phy(9)
• isci_host_completion_routine(9)
• sci_controller_stop(9)
• sci_controller_reset(9)
• isci_host_deinit(9)
• sci_controller_set_interrupt_coalescence(9)
• isci_host_init(9)
• sci_controller_allocate_remote_node_context(9)
• sci_controller_complete_io(9)

fr fr, this came out of ./drivers/scsi/isci — dated October 2026 — and it's still serving sci_controller_start_task(9) energy. periodt. 💅✨