regulator_lock_nested(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, welcome to regulator_lock_nested(9) from the Kernel API Manual πŸ’… β€” this one is literally just β€œlock a single regulator,” and that’s the whole assignment.

regulator_lock_nested β€” lock a single regulator. periodt. πŸŽ€

✨ SYNOPSIS ✨

int regulator_lock_nested (struct regulator_dev *rdev , struct
       ww_acquire_ctx *ww_ctx );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • rdev β€” regulator source. yes bestie, the regulator in question πŸ‘‘
  • ww_ctx β€” w/w mutex acquire context. that’s the context for the w/w mutex, okay? πŸ’…

πŸ’– DESCRIPTION πŸ’–

Here’s the vibe: one task can call this function many times on a single regulator, and its mutex will be locked only once. iconic behavior, honestly. ✨

If a task calling this function is other than the one that initially locked the mutex, it will wait on the mutex. that’s it, that’s the lore. 🫢

🌈 RETURN 🌈

0 on success, or a negative error number on failure. slay when it’s 0, sad little negative number when it’s not 😭

πŸŽ€ SEE ALSO πŸŽ€

mwah πŸ’‹ source/version: ./drivers/regulator Β· date: October 2026 Β· page: regulator_lock_nested(9) β€” okay bye bestie, go lock that single regulator πŸŒΈπŸ¦‹

πŸ“¦ where this page comes from