ccio_probe(9)

🦋 NAME 🦋

ok so ccio_probe — bestie, it's literally the vibe check that decides whether ccio should claim this device or not 💅

---

✨ SYNOPSIS ✨

int ccio_probe (struct parisc_device *dev );

---

🎀 ARGUMENTS 🎀

• dev — the device that just got found 👀 like, it's been spotted, and now we gotta figure out what to do with it

---

💖 DESCRIPTION 💖

Okay so here's the whole thing, no cap: this function determines if ccio should claim this chip — in which case it returns 0 — or not claim it, in which case it returns 1 🌸

And if it does claim the chip? Then it initializes the chip and tells the other partners in crime that they have work to do 🫶 like a group chat message going out to the whole squad, "we're up, let's go" ✨

fr fr, the return values are backwards from what your instincts say — 0 means "yes, mine", 1 means "nope, not mine". lowkey iconic of it 💅

---

👑 SEE ALSO 👑

Kernel file ./drivers/parisc/ccio-dma.c — plus the whole extended friend group 🌈:

• ccio_alloc_range(9)
• ccio_free_range(9)
• ccio_io_pdir_entry(9)
• ccio_clear_io_tlb(9)
• ccio_mark_invalid(9)
• ccio_dma_supported(9)
• ccio_map_single(9)
• ccio_unmap_phys(9)
• ccio_alloc(9)
• ccio_free(9)
• ccio_map_sg(9)
• ccio_unmap_sg(9)
• ccio_find_ioc(9)
• ccio_get_iommu(9)
• ccio_ioc_init(9)
• ccio_init(9)

---

aaaand that's the page!! 🎀 brought to you live from ./drivers/parisc, dated October 2026, filed under ccio_probe(9) — from the Kernel API Manual, mwah 💋 go read the rest of the gang, ily, bye 🦋💜