quicki2c_dev_init(9)

✨ quicki2c_dev_init — Kernel API Manual ✨

okay so bestie, we're looking at quicki2c_dev_init(9) from the Kernel API Manual today and honestly? it's giving "let me set up your whole device for you" energy 💅 this is the function that kicks off a QuickI2C device and gets the THC hardware actually, y'know, alive.

---

🌸 NAME 🌸

quicki2c_dev_init — Initialize QuickI2C device 🎀

✨ SYNOPSIS ✨

struct quicki2c_device * quicki2c_dev_init (struct pci_dev *pdev , void
__iomem *mem_addr , const struct quicki2c_ddata *ddata );

💖 ARGUMENTS 💖

• pdev — a pointer to the THC PCI device, no cap 🫶
• mem_addr — the pointer of MMIO memory address, like the actual doorway to the memory-mapped registers ✨
• ddata — points to the quicki2c_ddata structure 🌸

🔥 DESCRIPTION 🔥

So what it does: it allocs the quicki2c_device structure, initializes the THC device, and then configures THC to HIDI2C mode. iconic. it's basically the main character of device bring-up 👑

And if that all goes well? it enables the THC hardware interrupt. slay ⚡

🦋 RETURN 🦋

Pointer to the quicki2c_device structure if success, or NULL on failure. that's the whole vibe check — non-NULL means we ate, NULL means something went sideways 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/hid/intel-thc-hid/intel-quicki2c/pci-quicki2c.c — go read it, iykyk 📖

• quicki2c_acpi_get_dsm_property(9)
• quicki2c_acpi_get_dsd_property(9)
• quicki2c_get_acpi_resources(9)
• quicki2c_irq_quick_handler(9)
• try_recover(9)
• quicki2c_irq_thread_handler(9)
• quicki2c_dev_deinit(9)
• quicki2c_dma_adv_enable(9)
• quicki2c_dma_adv_disable(9)
• quicki2c_dma_init(9)
• quicki2c_dma_deinit(9)
• quicki2c_alloc_report_buf(9)
• quicki2c_remove(9)
• quicki2c_shutdown(9)

---

anyway that's the tea 🍓 this page comes from ./drivers/hid/intel-thc-hid/in... and it's dated October 2026, and the whole thing is filed under quicki2c_dev_init(9). mwah, go forth and init your devices bestie 💜🧚