spi_schedule_dv_device(9)

💅 spi_schedule_dv_device 💅

okay bestie, welcome to the Kernel API Manual page for spi_schedule_dv_device — she’s giving “domain validation, but make it scheduled” energy and honestly? iconic. 🎀

✨ NAME ✨

spi_schedule_dv_device — schedule domain validation to occur on the device 💫

🦋 SYNOPSIS 🦋

void spi_schedule_dv_device (struct scsi_device *sdev );

🌸 ARGUMENTS 🌸

• sdev — the device to validate. that’s her. the main character device. 👑

🔥 DESCRIPTION 🔥

okay so real talk: this is identical to spi_dv_device above, except the DV is scheduled to occur in a workqueue later. yes bestie, she’s deferred — not doing the domain validation right this second, she’s putting it on the workqueue’s to-do list. 💅

and the allocation situation? all memory allocations are atomic, which means you can call this from any context — including contexts that are holding SCSI locks. no cap, she’s safe like that. 🔒✨

🌈 SEE ALSO 🌈

• Kernel file ./drivers/scsi/scsi_transport_spi.c
• spi_dv_device(9)
• spi_display_xfer_agreement(9)
• spi_populate_tag_msg(9)

go read those if you want the full lore, iykyk 🫶

mwah 💖 sign-off time: source/version ./drivers/scsi, date October 2026, page spi_schedule_dv_device(9) — she ate and left no crumbs. periodt. 🎀