regulator_unlock_two(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… regulator_unlock_two β€” like, the Kernel API Manual page, bestie πŸŽ€

okay so this is regulator_unlock_two(9) from the Kernel API Manual and it's genuinely the shortest little icon β€” it does exactly one thing and does it flawlessly, no notes πŸ’–


✨ NAME ✨

regulator_unlock_two β€” unlock two regulators. that's it. that's the whole job. two of them. unlocked. slay πŸ¦‹


✨ SYNOPSIS ✨

void regulator_unlock_two (struct regulator_dev *rdev1 , struct
       regulator_dev *rdev2 , struct ww_acquire_ctx *ww_ctx );

look at her. void return, three params, zero drama. main character energy fr fr πŸ‘‘


✨ ARGUMENTS ✨

  • rdev1 β€” the first regulator. the blueprint. the one you met first πŸ’œ
  • rdev2 β€” the second regulator. the plus-one. the duo partner 🫢
  • ww_ctx β€” the w/w mutex acquire context. yes bestie, the wound/wait mutex situation β€” it's the context, it's required, don't come for me πŸ™ˆ

✨ DESCRIPTION ✨

The inverse of regulator_lock_two. that's literally the entire description and honestly? iconic. no cap. it undoes the thing, it's the anti-lock, the reverse uno card, periodt ✨

lowkey important: inverse of regulator_lock_two means you pair these two up β€” lock with one, unlock with the other. mismatched pairs are giving chaos πŸ’€

✨ SEE ALSO ✨

Kernel file ./drivers/regulator/core.c β€” and like, the entire extended family:

like, the whole regulator friend group showed up to the function. obsessed 🌈


anyway that's the page, bestie β€” ./drivers/regulator source, version date October 2026, regulator_unlock_two(9) out here keeping it πŸ’― the whole time. go unlock your two regulators, you got this πŸ’…πŸ’–βœ¨

πŸ“¦ where this page comes from