fwnode_reset...ol_array_get(9)

💅 fwnode_reset...ol_array_get(9)

okay so bestie, you're in the Kernel API Manual and this page is literally all about fwnode_reset_control_array_get — no cap, that's the whole vibe here. Buckle up 🎀

---

✨ NAME ✨

fwnode_reset_control_array_get — get a whole list of reset controls using a firmware node. That's it, that's the girlboss job description 💖

---

🌸 SYNOPSIS 🌸

struct reset_control * fwnode_reset_control_array_get (struct
       fwnode_handle *fwnode , enum reset_control_flags flags );

that's the whole signature, copy it exactly pls 🙈

---

🦋 ARGUMENTS 🦋

• fwnode — the firmware node for the device that's requesting the reset controls array. like, whose resets are these? this one. 💫
• flags — tells you whether the reset controls are shared, optional, or acquired. vibe check on the flags, basically ✨

---

💅 DESCRIPTION 💅

Returns a pointer to the allocated reset_control on success — or an error on failure. That's the whole deal, iconic and simple 🫶

---

🌈 SEE ALSO 🌈

okay this list is lowkey long but we're doing all of it, main character energy only 👑

• Kernel file ./drivers/reset/core.c
• struct reset_control(9)
• struct reset_control_array(9)
• struct reset_gpio_lookup(9)
• fwnode_reset_simple_xlate(9)
• reset_controller_register(9)
• reset_controller_unregister(9)
• devm_reset_controller_register(9)
• reset_control_reset(9)
• reset_control_bulk_reset(9)
• reset_control_rearm(9)
• reset_control_assert(9)
• reset_control_bulk_assert(9)
• reset_control_deassert(9)
• reset_control_bulk_deassert(9)
• reset_control_status(9)
• reset_control_acquire(9)
• reset_control_bulk_acquire(9)
• reset_control_release(9)
• reset_control_bulk_release(9)
• reset_control_put(9)
• reset_control_bulk_put(9)
• __device_reset(9)
• fwnode_reset_control_get_count(9)
• devm_reset_control_array_get(9)
• reset_control_get_count(9)

---

and that's the page bestie, fr fr 🍓

source location is ./drivers/reset, dated October 2026 — mwah, bye, go reset some things responsibly 💜✨