cvs_schedule_and_wait(9)

✨ cvs_schedule_and_wait(9) ✨

okay so bestie, welcome to the Kernel API Manual 💖 we are literally about to get into cvs_schedule_and_wait(9), and it’s giving “schedule the polling work, then wait for it to be done” energy. no cap.

---

🎀 NAME 🎀

cvs_schedule_and_wait — Schedule polling work then wait for completion 💅

---

🦋 SYNOPSIS 🦋

int cvs_schedule_and_wait (struct icvs *ctx , unsigned int work_delay_ms
, unsigned long wait_jiffies );

---

🌸 ARGUMENTS 🌸

• ctx — CVS device context. literally the device’s whole vibe container 🫶
• work_delay_ms — Delay in milliseconds before polling work executes. yes bestie, it waits that many ms before the polling work does its thing ⏳
• wait_jiffies — Timeout (jiffies) to wait for cmd completion. this is the “how long are we willing to wait” number, measured in jiffies ✨

---

💜 DESCRIPTION 💜

okay so picture this: it queues ctx->work to run after work_delay_ms, and then it waits up to wait_jiffies for ctx->cmd_completion. that’s the whole arc 😌💅

---

🔥 RETURN 🔥

• 0 on success 🎉
• -ETIMEDOUT on timeout 😭
• negative errno on error 💀

---

👑 SEE ALSO 👑

the kernel file is ./drivers/media/i2c/cvs/core.c, and the whole squad is right here:

• cvs_set_quirks(9)
• cvs_read_i2c(9)
• cvs_write_i2c(9)
• cvs_checksum(9)
• cvs_wait_wake_or_sleep(9)
• cvs_config_mipi(9)
• cvs_get_device_state(9)
• cvs_get_device_caps(9)
• cvs_hw_init(9)
• cvs_irq_handler(9)
• cvs_reset(9)
• cvs_recv(9)
• cvs_send(9)
• cvs_set_link_owner(9)
• cvs_configure_dev_caps(9)
• cvs_core_probe(9)
• cvs_probe(9)
• cvs_core_remove(9)
• cvs_remove(9)
• cvs_suspend(9)
• cvs_resume(9)
• cvs_runtime_resume(9)
• cvs_runtime_suspend(9)
• cvs_init(9)
• cvs_exit(9)

---

kisses bestie, this page is from ./drivers/media/i2c/cvs, October 2026 💖✨