cvs_recv(9)
π cvs_recv(9) β like, the delayed work handler that keeps checking if your command is done yet
okay bestie, welcome to the Kernel API Manual entry for cvs_recv(9) β yes that's the manual name, we're being fancy today β¨
πΈ NAME πΈ
cvs_recv β the delayed work handler that polls for command completion (it's giving "are we there yet" but make it kernel ππ¨)
β¨ SYNOPSIS β¨
void cvs_recv (struct work_struct *work );
that's it. that's the whole signature. no cap π«Ά
π ARGUMENTS π
workβ the embeddeddelayed_workmember. literally the work struct that's tucked inside, it's not a standalone thing, it's embedded, iykyk π
π¦ DESCRIPTION π¦
okay so here's the vibe: cvs_recv re-reads the device state π. if device_busy is still set, it just re-schedules itself β like, "not yet, bestie, try again later" π. otherwise? it stores the state into wq_resp and completes the command. slay, done, periodt π
π SEE ALSO π
kernel file ./drivers/media/i2c/cvs/core.c β and honestly the whole friend group is here:
cvs_set_quirks(9)cvs_read_i2c(9)cvs_write_i2c(9)cvs_checksum(9)cvs_schedule_and_wait(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_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)
ok and one last thing: this page lives at./drivers/media/i2c/cvs, dated October 2026, and it's thecvs_recv(9)entry π thanks for coming to my ted talk, mwah π§π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms