devm_reset_c...ive_released(9)

📦 version 7.3.1, in nixpkgs unstable

✨ devm_reset_control_bulk_get_exclusive_released ✨

okay so bestie, we're in the Kernel API Manual today (yes, the Kernel API Manual, that's the whole vibe) and we're about to talk about devm_reset_control_bulk_get_exclusive_released. long name? yes. iconic? also yes. let's get into it 💅

🌸 NAME 🌸

devm_reset_control_bulk_get_exclusive_released — the resource managed version of reset_control_bulk_get_exclusive_released(). it's giving "same energy, but the cleanup is handled for you" 🫶

✨ SYNOPSIS ✨

int devm_reset_control_bulk_get_exclusive_released (struct device *dev ,
int num_rstcs , struct reset_control_bulk_data *rstcs );

🎀 ARGUMENTS 🎀

  • dev — the device that's gonna get reset by the controller. it's the main character here tbh 👑
  • num_rstcs — how many entries live in the rstcs array. like, the headcount 🌈
  • rstcs — an array of struct reset_control_bulk_data with the reset line names already set. this one's already dressed and ready to go 🦋

💖 DESCRIPTION 💖

so this is the managed reset_control_bulk_get_exclusive_released. lowkey the best part: for reset controllers returned from this function, reset_control_put gets called automatically when the driver detaches. no manual cleanup era, we love to see it 😭✨

if you want the full lore, go read reset_control_bulk_get_exclusive_released — it has all the details.

🔥 SEE ALSO 🔥

Kernel file ./include/linux/reset.h plus a whole friend group of functions, fr fr:

and that's the page, bestie 🧚 this little gem comes to you from ./include/linux, dated October 2026 — slay, go forth and manage your resets 💜🎀

📦 where this page comes from