enclosure_find(9)

💖 enclosure_find(9) 💖

okay bestie, welcome to the enclosure_find(9) page from the Kernel API Manual — yes we are in kernel land, and yes it's giving very niche but very iconic. 🧚✨

---

✨ NAME ✨

enclosure_find — find an enclosure given a parent device 🫶

---

🌸 SYNOPSIS 🌸

struct enclosure_device * enclosure_find (struct device *dev , struct
       enclosure_device *start );

---

🎀 ARGUMENTS 🎀

• dev — the parent to match against. literally the thing we're checking against, no cap.
• start — Optional enclosure device to start from (NULL if none). iykyk, it's the "begin here" spot.

---

🦋 DESCRIPTION 🦋

so the way this works: enclosure_find looks through the list of registered enclosures to find all those with dev as a parent. If no enclosure is found, it returns NULL — that's the vibe check failing, bestie 😭.

start can be used as a starting point to obtain multiple enclosures per parent. It should begin with NULL, and then be set to each returned enclosure device. That's the whole loop situation. 💫

It obtains a reference to the enclosure class device, and that reference must be released with put_device — don't forget, or the kernel will be side-eyeing you fr fr.

If start is not NULL, a reference must be taken on it which is released before returning. This allows a loop through all enclosures to exit with only the reference on the enclosure of interest held. iconic behavior, honestly 👑.

Note that the dev may correspond to the actual device housing the enclosure, in which case no iteration via start is required. so don't do extra work for no reason, bestie 💅.

---

💜 SEE ALSO 💜

Kernel file ./drivers/misc/enclosure.c and the whole friend group:

• enclosure_for_each_device(9)
• enclosure_register(9)
• enclosure_unregister(9)
• enclosure_component_alloc(9)
• enclosure_component_register(9)
• enclosure_add_device(9)
• enclosure_remove_device(9)

---

kisses, this page is straight outta ./drivers/misc and dated October 2026 — bestie, that's the source and date, and we are done 💖✨