reset_control_get_exclusive(9)

📦 version 7.3.1, in nixpkgs unstable

💅 reset_control_get_exclusive — the Kernel API Manual page you didn't know you needed

okay so bestie, welcome to the Kernel API Manual entry for reset_control_get_exclusive(9), and trust me when I say this one is lowkey iconic. it's giving "I want my own reset controller and I don't want to share" energy, and honestly? relatable.

✨ NAME ✨

reset_control_get_exclusive — lookup and obtain an exclusive reference to a reset controller 🎀

🌸 SYNOPSIS 🌸

struct reset_control * reset_control_get_exclusive (struct device *dev ,
       const char *id );

like, that's the whole vibe right there. two args, one return value, no drama (until -EBUSY shows up 💀).

🦋 ARGUMENTS 🦋

  • dev — the device that's gonna get reset by the controller. it's the main character in this operation, fr fr.
  • id — the reset line name. just the name, bestie. that's it.

💖 DESCRIPTION 💖

so what does it do?? it returns a struct reset_control or an IS_ERR condition containing errno. periodt. 💅

and here's the tea 🍓: if this function is called more than once for the same reset_control, it will return -EBUSY. not me calling twice and getting yelled at 😭 that's the exclusive part doing its job — one owner only, no plus-ones.

highly recommend checking out reset_control_get_shared if you actually want the details on shared references to reset-controls. that's the whole "we can share this" page, this is the "no, it's mine" page. 💀

also: use of id names is optional. so if you don't have one, you're still valid, bestie 🫶

🔥 SEE ALSO 🔥

okay this list is long — like, scroll-for-days long — but every single one of these is here so don't skip:

like I said. scroll city. but now you know them all and that's a slay 🌈

that's the whole page, bestie 💜 — brought to you straight out of ./include/linux, dated October 2026, version 9 of the manual. go reset something responsibly, and remember: exclusive means exclusive 👑✨

📦 where this page comes from