of_reset_control_get_shared(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

of_reset_control_get_shared — bestie, this is the one that goes and looks up a reset controller and hands you a shared reference to it. Like, you're not the only one holding it, and that's literally the whole point ✨

(oh also, hi, this is the Kernel API Manual — welcome to the function-specific corner of the kernel docs 🎀)

✨ SYNOPSIS ✨

struct reset_control * of_reset_control_get_shared (struct device_node
*node , const char *id );

🌸 ARGUMENTS 🌸

  • node — the device that's getting reset by the controller 👑 like, this is the main character here.
  • id — the name of the reset line 🎀

💖 DESCRIPTION 💖

Okay so here's the tea 🫖 — when a reset-control is shared, the behaviour of reset_control_assert / deassert is genuinely different, no cap. The reset-core keeps track of a deassert_count and it will only (re-)assert the reset after reset_control_assert has been called as many times as reset_control_deassert was called. It's giving ✨reference counting energy✨ ngl. Also, go peek at the remark about shared reset-controls over in the reset_control_assert docs 👀

⚠️ Real talk, bestie — calling reset_control_assert without first calling reset_control_deassert is not allowed on a shared reset control. Periodt. And calling reset_control_reset is also not allowed on a shared reset control. Not me warning you twice 😭

It returns a struct reset_control or an IS_ERR condition containing errno 💀

Use of id names is optional 🦋 (so like, optional optional, not a vibe check you have to pass)

🔥 SEE ALSO 🔥

Kernel file ./include/linux/reset.h — and honestly the whole reset-core friend group 💜:

okay that's the whole page, you ate that 💅 this lil doc lives in ./include/linux and it's dated October 2026 — so it's from the future, iconic behavior honestly 🦋✨

📦 where this page comes from