cvs_set_quirks(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

cvs_set_quirks — the little matchmaker that pairs a device's VID/PID with its quirk flags ✨ (straight out of the Kernel API Manual, no cap)

🎀 SYNOPSIS 🎀

void cvs_set_quirks (struct icvs *ctx , u16 vid , u16 pid );

🦋 ARGUMENTS 🦋

  • ctx — your CVS device context 💖 this is the glow-up target, the thing that gets its quirk flags filled in.
  • vid — Vendor ID 🏷️ like the device's last name, fr fr.
  • pid — Product ID 🔖 the first name, so the duo is complete.

✨ DESCRIPTION ✨

Okay so here's the vibe 👑 — it goes looking through the quirk table for a VID/PID that matches, and when it finds its icon it populates ctx->quirks with the matching quirk flags. Slay.

And if nothing matches? 🫶 No drama at all — quirks just gets set to 0. Empty. A fresh start. Main character energy of the blank-slate variety 😌

🌈 SEE ALSO 🌈

Kernel file ./drivers/media/i2c/cvs/core.c, plus the whole friend group 🧚‍♀️ (all of these are (9) sections, iykyk):

  • cvs_read_i2c
  • cvs_write_i2c
  • cvs_checksum
  • cvs_schedule_and_wait
  • cvs_wait_wake_or_sleep
  • cvs_config_mipi
  • cvs_get_device_state
  • cvs_get_device_caps
  • cvs_hw_init
  • cvs_irq_handler
  • cvs_reset
  • cvs_recv
  • cvs_send
  • cvs_set_link_owner
  • cvs_configure_dev_caps
  • cvs_core_probe
  • cvs_probe
  • cvs_core_remove
  • cvs_remove
  • cvs_suspend
  • cvs_resume
  • cvs_runtime_resume
  • cvs_runtime_suspend
  • cvs_init
  • cvs_exit
💀 Reminder bestie: no guessing at behaviour, no made-up flags — everything above is exactly what the page says. Go read the source if you want more tea 🍓

Okay that's the whole page, mwah 💋🫶 — brought to you by ./drivers/media/i2c/cvs, October 2026 edition, and remember: cvs_set_quirks(9) loves you and wants you to match your VID/PID correctly 🌸✨💜

📦 where this page comes from