comp_probe(9)

✨ comp_probe(9) ✨

okay so this is a page from the Kernel API Manual, bestie — it's comp_probe, and it's literally the probe function of the driver module 💅

---

🌸 NAME 🌸

comp_probe — probe function of the driver module

---

🎀 SYNOPSIS 🎀

int comp_probe (struct most_interface *iface , int channel_id , struct
most_channel_config *cfg , char *name , char *args );

---

🦋 ARGUMENTS 🦋

• iface — pointer to the interface instance 🫶
• channel_id — the channel index / ID, iykyk
• cfg — pointer to the actual channel configuration
• name — name of the device to be created (yes, you get to name it, main character energy)
• args — pointer to an array of component parameters, and those come from configfs ✨

---

💖 DESCRIPTION 💖

So what does it actually do? It allocates a channel object and creates the device node in /dev 👑

Returns 0 on success, or an error code otherwise. That's it, that's the vibe check 🌈

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/most/most_cdev.c, plus the whole squad:

• comp_open(9)
• comp_close(9)
• comp_write(9)
• comp_read(9)
• comp_disconnect_channel(9)
• comp_rx_completion(9)
• comp_tx_completion(9)

---

and that's a wrap, bestie 🍓 this one lives in ./drivers/most and it's dated October 2026 — go forth and probe, no cap 💜