cvs_hw_init(9)

💅 cvs_hw_init(9) — like, the Kernel API Manual page, bestie ✨

Ok so real talk, this is cvs_hw_init from section 9 of the Kernel API Manual, and she's the little "hello?? are you actually a prefix device??" moment of the whole driver 🫶

---

🎀 NAME 🎀

cvs_hw_init — probe the device for prefix support and then apply the matching quirks 💖

---

✨ SYNOPSIS ✨

int cvs_hw_init (struct icvs *ctx );

---

🌸 ARGUMENTS 🌸

• ctx — the CVS device context, the main character we're doing all this for 👑

---

🦋 DESCRIPTION 🦋

So first thing: it sends GET_DEV_VID_PID and basically does a vibe check looking for a 32-bit prefix 🔍

If it matches ICVS_PREFIX_VAL, it sets ctx->prefix and that's what gets used for all the reads that come after — slay, the vibe is confirmed 💅

Then it reads the VID/PID and applies whatever quirks match. Because of course there are quirks. There are always quirks 😭

And good news: GET_DEV_VID_PID is supported by all protocol versions, no cap, so you're not gonna hit a version that's like "new phone who dis" 🙈

---

⭐ RETURN ⭐

0 on success, or a negative errno if it's giving "that didn't work" energy 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/media/i2c/cvs/core.c — that's the home base, iykyk 🏠
• 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_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)

---

That's the whole page, no notes 💜 It lives at ./drivers/media/i2c/cvs, it's dated October 2026, and this is the cvs_hw_init(9) entry — periodt, go read the other ones too 🎀✨🦋