event_device_probe(9)

💖 event_device_probe(9) 💖

ok so bestie, welcome to the Kernel API Manual, section 9 — this is the page for event_device_probe, and honestly? it's giving "small function, big responsibilities." let's get into it 🎀

---

✨ NAME ✨

event_device_probe — the callback that fires when a brand-new device is being created. literally the "hi bestie welcome to the world" moment for a device 🌸

---

✨ SYNOPSIS ✨

int event_device_probe (struct platform_device *pdev );

---

✨ ARGUMENTS ✨

• pdev — the platform device that we will be receiving events from. that's our girl 🫶 she's the one feeding us the events.

---

✨ DESCRIPTION ✨

okay so here's the vibe: this function goes and finds a free minor number for the device, then allocates and initializes some device data, and finally creates a new device and a char dev node. three-step glow-up, no cap ✨

now the important part — the device data gets freed in free_device_data, and that gets called when dev_data->dev is released. and when does that happen? only after all references to dev_data->dev are dropped. and that, bestie, happens once both of these things have gone down:

1. event_device_remove has been called, and
2. every opened file descriptor has been released.

so yeah — both conditions, not one. don't come for me, that's just how the lifecycle works 😭💀

---

✨ RETURN ✨

• 0 on success 🎉
• a negative error code on failure 😭

---

✨ SEE ALSO ✨

• Kernel file ./drivers/platform/chrome/wilco_ec/event.c
• struct ec_event(9)
• struct ec_event_queue(9)
• struct event_device_data(9)
• enqueue_events(9)
• event_device_notify(9)
• event_read(9)
• free_device_data(9)

go read them, iykyk 👑

---

and that's the whole page, bestie 💅 this lil gem comes to you from ./drivers/platform/chrome/wilc... (yes that's the source line, truncated exactly like that, i don't make the rules 🫠) and it's dated October 2026 — so go forth, probe those devices, and slay 🌈⭐💜